release: promote main - #107
Merged
Merged
Conversation
The titler regenerated the title on every push once it had written one, so a pull request's subject was whatever its *last* commits looked like. #105 carried the whole website-tracking feature and was retitled `fix(ci)` by its final push, squashed onto main under that subject, and released as a patch whose notes mention none of it. A generated title is now left alone unless it stops being a conventional commit or stops covering the branch, and no title — generated or typed — may release less than the commits behind it: `floor_of` takes the strongest bump on the branch and `generate` raises its proposal to meet it. A branch holding a `feat` cannot ship as a `fix`, and one holding a breaking change cannot ship without the `!`. Over-releasing is the safe direction; losing a feature out of the changelog is not.
A first-party script on the marketing site, a collector in the API, and one rule: a form submission becomes a contact. Page views, click labels and first/last-touch attribution hang off that, with a 90-day retention sweep, an hourly contact cap and a per-minute event budget. The work landed in 815a832. The auto-titler had retitled its pull request `fix(ci)` on the last push, so it squashed onto main under that subject and released as a patch whose notes describe only the guard fix. This commit carries no code — it exists so the changelog and the version say what actually shipped. See docs/tracking.md.
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.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.
Everything on
mainthatreleasedoes not have yet. Merging this is what puts it infront of users, because
releaseis what a deploy and a plain clone both point at.Nothing releasable is waiting — no version bump will ride along with this.
Merge it with a merge commit, not a squash: a squash would give
releasea newcommit of its own, and the tags on
mainwould stop being ancestors of what you shipped.