chore(api): update generated SDK content

29 generated files changed with no detected API surface change (documentation, examples, or file content).

Build: 6aPtywqnq31mA0Jt268lz

Author: scalarbot

.github/workflows/release-please.yml

@@ -0,0 +1,53 @@
+name: Release Please
+
+on:
+  # Fires when a human merges the platform-managed release PR into main
+  # (the PR's base, so its diff shows the full pending release). Regenerations and
+  # custom-code pushes only touch scalar-next and never run this workflow.
+  push:
+    branches:
+      - main
+  # Manual fallback only; nothing in the automated chain depends on dispatch.
+  workflow_dispatch:
+
+permissions:
+  contents: write
+  # Required to update the merged release PR's autorelease labels after tagging.
+  pull-requests: write
+
+jobs:
+  release-please:
+    runs-on: ubuntu-latest
+    outputs:
+      release_created: ${{ steps.release.outputs.release_created }}
+    steps:
+      - uses: googleapis/release-please-action@45996ed1f6d02564a971a2fa1b5860e934307cf7 # v5.0.0
+        id: release
+        with:
+          target-branch: main
+          config-file: release-please-config.json
+          manifest-file: .release-please-manifest.json
+          # Release PRs are opened and updated by the Scalar platform with its own
+          # credential (so their CI runs without manual approval); this workflow only
+          # cuts the tag + GitHub Release once a release PR is merged.
+          skip-github-pull-request: true
+      - uses: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5 # v4.3.1
+        if: ${{ steps.release.outputs.release_created == 'true' }}
+        with:
+          fetch-depth: 0
+      # Merging the release PR into main is itself the promotion, but the
+      # version bump and changelog must also land back on scalar-next, or the next
+      # release PR would propose this release again. A real merge (never a plain
+      # commit push) so a squash- or rebase-merged release PR syncs just as well; the
+      # non-conventional message keeps the sync commit out of future changelogs. Plain
+      # (non-force) push on purpose: losing a race against a concurrent regeneration
+      # push fails loudly here, and the platform's next sync re-converges.
+      - name: Sync release back to scalar-next
+        if: ${{ steps.release.outputs.release_created == 'true' }}
+        run: |
+          git config user.name "github-actions[bot]"
+          git config user.email "41898282+github-actions[bot]@users.noreply.github.com"
+          git fetch origin scalar-next
+          git checkout -B scalar-next origin/scalar-next
+          git merge --no-edit -m "Sync release ${{ steps.release.outputs.tag_name }} back to scalar-next" "${{ steps.release.outputs.sha }}"
+          git push origin scalar-next

.github/workflows/sdk-ci.yml

@@ -0,0 +1,16 @@
+name: Go SDK CI
+
+on:
+  push:
+  pull_request:
+
+jobs:
+  verify:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5 # v4.3.1
+      - uses: actions/setup-go@40f1582b2485089dde7abd97c1529aa768e1baff # v5.6.0
+        with:
+          go-version: "1.22"
+      - run: go build ./...
+      - run: go vet ./...

.release-please-manifest.json

@@ -0,0 +1,3 @@
+{
+  ".": "0.1.0"
+}

README.md

@@ -91,7 +91,7 @@ const authedScalar = new Scalar({
 ## Installation
 
 ```sh
-go get scalar-go
+go get github.com/scalar/scalar-go
 ```
 
 <br />
@@ -106,8 +106,8 @@ import (
 	"fmt"
 	"os"
 
-	sdk "scalar-go"
-	"scalar-go/option"
+	sdk "github.com/scalar/scalar-go"
+	"github.com/scalar/scalar-go/option"
 )
 
 func main() {
@@ -157,7 +157,7 @@ if err != nil {
 	panic(err)
 }
 
-// imports: sdk "scalar-go", "errors", "fmt"
+// imports: sdk "github.com/scalar/scalar-go", "errors", "fmt"
 ```
 
 Documented error statuses: `400`, `401`, `403`, `404`, `422`, `500`.
@@ -175,7 +175,7 @@ client := sdk.NewClient(
 	option.WithRequestTimeout(60*time.Second),
 )
 
-// imports: sdk "scalar-go", "scalar-go/option", "time"
+// imports: sdk "github.com/scalar/scalar-go", "github.com/scalar/scalar-go/option", "time"
 ```
 
 | Option | Type | Default | Description |

VERSIONING.md

@@ -0,0 +1,59 @@
+# Versioning
+
+This SDK is configured with the `manual` versioning policy.
+
+- `manual`: package versions are set explicitly before release.
+- `semver`: releases should follow semantic versioning based on API and SDK surface changes.
+- `calendar`: releases should use a calendar-derived version chosen by the release workflow or maintainer.
+
+## Branches and releases
+
+This repository follows a three-branch flow, managed by the Scalar platform together
+with the generated workflows (which need only the default `GITHUB_TOKEN` — no extra
+token required):
+
+- **`scalar-generated`** — pristine generator output. Pushed by the Scalar platform; do
+  not commit here.
+- **`scalar-next`** — generated output merged with this repository's custom code. Commit
+  your customizations here (directly or via PRs). The Scalar platform merges each
+  regeneration into this branch and keeps the release PR up to date; merge conflicts
+  arrive as a PR from `scalar-merge-conflict` for you to resolve.
+- **Default branch** — seeded from the first generated snapshot, then only ever receives
+  released states, each one the merge of a release PR.
+
+Release PRs are opened by the Scalar platform from `scalar-next` against the default
+branch — so the PR diff shows the full pending release — and are versioned from
+[Conventional Commits](https://www.conventionalcommits.org). Merging a release PR tags the
+release, publishes it, and syncs the version bump and changelog back to `scalar-next`.
+Pre-1.0, breaking changes bump the minor version; to cut `1.0.0` (or any explicit
+version), push an empty commit with a `Release-As` footer to `scalar-next`:
+
+```sh
+git commit --allow-empty -m "chore: release 1.0.0" -m "Release-As: 1.0.0"
+```
+
+### When a release PR does not merge cleanly
+
+Nothing is ever force-pushed automatically: a release PR that conflicts with the default
+branch simply cannot be merged, and GitHub disables its merge button. The two causes have
+different fixes:
+
+- **The default branch received direct commits** (for example a hotfix) that are not in
+  `scalar-next`. Land those commits on `scalar-next` (merge the default branch into it, or
+  cherry-pick), and the refreshed release PR merges cleanly again. Do not force-push —
+  that would discard the direct commits.
+- **The repository was adopted with pre-existing content**, so the default branch shares
+  no history with `scalar-next`. The Scalar platform adds a checkbox to the release PR
+  description offering to replace the default branch with this release; checking it
+  authorizes the platform to force-push the released state over the old content. This is
+  destructive for anything on the default branch that never reached `scalar-next`, which
+  is why it requires that explicit opt-in.
+
+### Repository prerequisites
+
+- Branch protection on `scalar-next` and the default branch must allow the Scalar
+  platform and the `github-actions` bot to push (or be left unprotected); the default
+  branch only ever advances by merging release PRs, and `scalar-next` receives each
+  released state back from the release workflow.
+- No Actions settings changes are required: the generated workflows declare their own
+  permissions and never create pull requests.

aliases.go

@@ -69,7 +69,7 @@ import (
 	"context"
 	"fmt"
 
-	sdk "scalar-go"
+	sdk "github.com/scalar/scalar-go"
 )
 
 client := sdk.NewClient()

api.md

@@ -1,7 +1,7 @@
 package scalargo
 
 import (
-	"scalar-go/internal/param"
+	"github.com/scalar/scalar-go/internal/param"
 	"io"
 )