chore(release): pipeline order align + finalize v0.2.0 changelog#25
Merged
chore(release): pipeline order align + finalize v0.2.0 changelog#25
Conversation
…v0.2.0 changelog
- Tag-driven version bump: `pnpm version "${GITHUB_REF#refs/tags/v}"`
so package.json follows the tag automatically, matching how
auth.provider releases work. Avoids the manual bump step.
- Pipeline order adjusted to `install -> build -> typecheck -> test`,
mirroring auth.provider/.github/workflows/release.yml.
- CHANGELOG: finalize [Unreleased] as [0.2.0] — 2026-04-24 (the
injection-mode release). Version follows proxy's own 0.x sequence
(v0.1.0 was the previous tag).
Does not adopt provider's draft->publish two-stage or npm publish
steps: auth.proxy is `"private": true`, so a single final Release is
sufficient.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…not npm package) auth.proxy is distributed as a Docker image — it is a runtime service, not a library. There is no npm publish step (now or planned), so the tag-driven pnpm version bump added in the previous commit has no consumer. package.json version stays at 0.0.0 in git; Docker image tags are the actual release identifier. Keep the install -> build -> typecheck -> test pipeline reorder from the previous commit — that improvement stands regardless of whether we publish to npm. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
There was a problem hiding this comment.
Pull request overview
Updates the release workflow to run the build earlier in CI and finalizes the changelog for the v0.2.0 release.
Changes:
- Reordered release workflow steps to run
buildbeforetypecheckandtest. - Updated
CHANGELOG.mdby converting the[Unreleased]section into a dated[0.2.0]release entry.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
CHANGELOG.md |
Replaces [Unreleased] with a versioned 0.2.0 entry dated 2026-04-24. |
.github/workflows/release.yml |
Reorders the workflow to run pnpm run build earlier in the pipeline. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
…ap pipeline order - CHANGELOG: re-add empty [Unreleased] section above [0.2.0] per Keep a Changelog convention. Future change sets accumulate under [Unreleased] and get renamed at the next release tag. - release.yml: swap order to typecheck -> test -> build. The earlier 'build -> typecheck' ran tsc twice (tsc --build already type-checks) and test is independent of the build artifact (vitest executes .mts source directly). typecheck-first fails fast on type errors before spending CI time on tests and build. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Non-goals
auth.proxy is a runtime service distributed as a Docker image, not an npm library. It is (and remains) `"private": true`. No npm publish step is added to release.yml — Docker image tags are the release identifier. The tag-driven `pnpm version` step from auth.provider's workflow is intentionally not copied.
Test plan
Follow-up
After merge, tag `v0.2.0` on develop to trigger the Release workflow and auto-generate GitHub Release notes from the injection-mode commit history.
🤖 Generated with Claude Code