release: bump version to 0.12.0, vendor 0.12.0 release feed#222
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Bumps package.json 0.11.0 -> 0.12.0 and refreshes tests/fixtures/release-feed.xml from the regenerated landing changelog. Keeps the release-version-sync guard (#211/#212 drift) green by tying the app's reported version to the published 0.12.0 release notes. Co-Authored-By: Claude Opus 4.8 <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
1 participant
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.
Bumps
package.json0.11.0 → 0.12.0 and refreshestests/fixtures/release-feed.xmlfrom the regenerated landing changelog.Why
After the 0.11.0 notes were published, six commits landed on
main— including a user-facing paywall fix (#211) and self-host LAN/IP TLS work (#212/#217, #220). This cuts 0.12.0 to capture them and keeps the app's reported version tied to the published release notes.Verification
tests/scripts/release-version-sync.test.ts(the bug: Articles incorrectly flagged as paywalled & settings menu doesn't display the installed version #211/bug: Can't deploy with docker #212 drift guard) — green:package.json== newest fixture entry == 0.12.0.tests/core/parser/release-feed-fixture.test.ts— green: the app's parser consumes the new fixture.tsc --noEmitclean.⚠ Merge order
Merge after feedzero-landing#24 (the changelog must publish first so first-launch auto-subscribe sees 0.12.0). The vendored fixture here was generated from that PR's
releases.xml.Follow-up (separate, with your go-ahead)
The
v0.11.0git tag points atc9317c2(package.json 0.9.0 there), so the published 0.11.0 Docker image reports 0.9.0. You approved re-pointingv0.11.0→3ab8ffb; I'll do that tag force-push after these merge.🤖 Generated with Claude Code