chore(release): v1.0.1 - #14
Merged
Merged
Conversation
Signed-off-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
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.
Release v1.0.1
Automated release pull request for
v1.0.1, drafted from the commits merged sincev1.0.0. Nothing is tagged or published until this pull request is merged.
What this changes
version1.0.0->1.0.1inpackage.json,packages/backend/package.jsonandpackages/frontend/package.json. The backendmanifest is read at runtime, so
GET /api/healthreports the new version.## [1.0.1] - 2026-09-15section inCHANGELOG.md, placed above the previousrelease and merged with any notes already staged for this one.
Review checklist
CHANGELOG.mddirectly on thisbranch before merging.
What happens on merge
The merge commit is tagged
v1.0.1and theRelease pipeline runs: it creates the GitHub
Release with generated notes, attaches the frontend bundle, and publishes the
custotal-backend:v1.0.1(API),custotal-backend:v1.0.1-tools(migrations) andcustotal-frontend:v1.0.1container images to GHCR. Every image carries the same tag, soCUSTOTAL_TAG=v1.0.1pins the whole stack, and no floatinglatestis published.Re-dispatching Release: prepare rebuilds this branch from
mainandoverwrites edits made here, so prefer to fix the branch in place.
Generated changelog draft
[1.0.1] - 2026-09-15
Security
caps the field at the RFC 5321 maximum (254 characters) before any matching, instead of a pattern
that backtracked.
Documentation
Maintenance