0.8.0: version the contact gate - #40
Merged
Merged
Conversation
0.7.0 was tagged and published to npm before #38 merged, so the release and the package named 0.7.0 contain the employer decision flow but not the contact gate. Two PRs hand-bumped to the same number and both merged cleanly, which is how a version stops identifying a build. No behaviour change. This is the number the contact gate ships under. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015xXMzJf85q87oeG3VEKHdJ
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.
v0.7.0 was tagged and published to npm at 11:04, before #38 merged at 11:20. So the release and the npm package named 0.7.0 carry the employer decision flow from #37 but not the contact gate from #38.
Two PRs hand-bumped to the same number and both merged cleanly. Nothing catches that, and the result is a version string that no longer identifies a build:
agenticjobs@0.7.0from npm and the 0.7.0 running in production are different code.No behaviour change here. This is just the number the contact gate ships under.
🤖 Generated with Claude Code