Repository navigation
[CASE-4844] Release 2.1.3 - #88
Merged
Merged
Conversation
The fixes from #87, released so consumers can pin a tag rather than master.
aitorlb
marked this pull request as ready for review
November 9, 2026 11:51
AlfonsoUceda
approved these changes
Nov 9, 2026
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.
Why
The fixes from #87 are on
masterbut in no release:VERSIONis still2.1.2and the changelog lists them under "Unreleased".toptal/career-services-backendnow takes the gem frommaster(toptal/career-services-backend#2451) and its Gemfile says to go back to a release once one is tagged.What
VERSION→2.1.3.## [2.1.3] - 2026-11-09, with an empty "Unreleased" heading kept above, as in the 2.1.2 release ([CASE-4447] Release 2.1.2 and fix the failing CI checks #84).After merge
Tag the merge commit
v2.1.3and push the tag. Nothing here runs on tags (no release workflow, nothing published), so the tag is only what consumers pin: career-services-backend#2451 then switches frombranch: 'master'totag: 'v2.1.3'. If the merge lands on another day, the changelog date is updated to match before tagging.🤖 Generated with Claude Code