Skip to content

Repository navigation

chore: publish alpha releases to latest #3

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
monarcode merged 1 commit into from
Oct 3, 2026
Merged

chore: publish alpha releases to latest #3

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .github/workflows/release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -87,7 +87,7 @@ jobs:
- name: Publish alpha to npm
env:
RELEASE_VERSION: ${{ inputs.version }}
run: npm publish "$RUNNER_TEMP/release/monarcode-session-kit-$RELEASE_VERSION.tgz" --tag next --access public --ignore-scripts
run: npm publish "$RUNNER_TEMP/release/monarcode-session-kit-$RELEASE_VERSION.tgz" --tag latest --access public --ignore-scripts
- name: Create GitHub prerelease and tag
env:
GH_TOKEN: ${{ github.token }}
Expand Down
4 changes: 2 additions & 2 deletions RELEASING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@

The `Release alpha` workflow is manually triggered. It releases an alpha version
already committed to `main`; it does not change versions or commit files.
It checks and packs with pnpm, publishes the verified tarball to npm using `next`,
It checks and packs with pnpm, publishes the verified tarball to npm using `latest`,
then creates a Git tag and GitHub prerelease at the workflow's commit.

## One-time npm setup
Expand Down Expand Up @@ -32,7 +32,7 @@ For this public repository/package, trusted publishing also generates provenance
2. Run `pnpm run check`, then commit and push those changes to `main`.
3. Open GitHub Actions → **Release alpha** → **Run workflow**. Choose `main`
and enter the exact package version, without a `v` prefix.
4. Verify the run succeeds, npm exposes the version through `next`, and the
4. Verify the run succeeds, npm exposes the version through `latest`, and the
matching GitHub prerelease exists.

The workflow rejects a different branch, invalid or mismatched versions, missing
Expand Down
Loading