chore(release): remove @semantic-release/git plugin + rename package to flow#165
Merged
jeziellopes merged 1 commit intodevelopfrom Apr 10, 2026
Merged
Conversation
…to flow - Remove @semantic-release/git: the plugin auto-commits CHANGELOG.md and package.json directly to main after every stable release. That commit is never in develop, causing conflicts on every subsequent develop → main PR. Removing it means semantic-release still tags, publishes GitHub releases and generates release notes — just without writing files back to the repo. - Remove @semantic-release/changelog: only relevant alongside the git plugin since nothing commits the generated file without it. - Rename package name from 'trading-engine' to 'flow' to match the repo. Signed-off-by: Jeziel Lopes <jeziellopes@gmail.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Problem
@semantic-release/gitauto-commitsCHANGELOG.md+package.jsondirectly tomainafter every stable release. That commit is never indevelop, so every subsequentdevelop → mainPR conflicts on those two files (this just happened with v1.1.0, requiring back-merge PR #163).Changes
@semantic-release/git— semantic-release still creates git tags, publishes GitHub releases, and generates release notes. It just no longer writes files back to the repo. No auto-commit = no conflict = no back-merge ever needed.@semantic-release/changelog— only useful alongside the git plugin; pointless without something to commit it.package.namefromtrading-engine→flow— aligns with the repo/project name.After this merges
PR #163 (back-merge to resolve the current conflict) still needs to land before PR #162 (develop → main). Once #162 merges, v1.2.0 is tagged and released — no files are committed back to main, so the next release cycle starts clean.