Comments (3)
by using a squash merge, you are rewriting history in a way that is losing the details you are describing. dont squash your release branches.
from semantic-release.
@travi we only squash the PR's into staging (default branch). PR's into main and LTS are not squashed.
from semantic-release.
It happens to us as well when we fast-forward merge a higher branch (e.g. develop
) into a pre-release branch, hence a backmerge. The pre-release branch release job overwrites channel info created by previous develop
release job.
In get-release-to-add.js
it looks like pre-release branches are ignored, which cause the channel overwrite instead of adding to the current content.
const higherChannels = branches
// Consider only releases of higher branches
.slice(branches.findIndex(({ name }) => name === branch.name) + 1)
// Exclude prerelease branches
.filter(({ type }) => type !== "prerelease")
.map(({ channel }) => channel || null);
Is it intentional to work like this?
Update:
Just read release notes for v23 and noticed that there is one note reference per tag. We are using v21 with a single reference.
Shouldn't this change prevent channel overwrite?
from semantic-release.
Related Issues (20)
- Unexpected Minor Version Bump in Beta Release Sequence HOT 9
- Missing Release Notes HOT 1
- Publishing a GitHub release & triggering another workflow HOT 2
- Allow --dry-run option to ignore configured release branches HOT 3
- An error occurred while running semantic-release: SyntaxError: Unexpected identifier 'assert' HOT 6
- Allow branches not under --heads (/ref/heads) to be used as release branches HOT 3
- --plugins CLI flag does not honor plugin configurations
- An error occurred while running semantic-release: Error: Cannot find module `@semantic-release/changelog` HOT 3
- releaserc didn't produce expected results HOT 7
- RangeError: Invalid time value HOT 7
- RangeError: Invalid time value HOT 3
- Add `--pre-release` option to "force" a prerelease on the current branch if possible
- Cannot pass build number to use in tag format HOT 28
- can't create new release on github HOT 1
- Fork
- Configure Semantic-Release to only show the latest package update in release notes
- Update file extensions to include .mjs on configuration docs page HOT 1
- Get current version and not only nextRelease.version
- Getting the error "The local branch <branch name> is behind the remote one, therefore a new version won't be published" during CI
- extract default config to a package HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from semantic-release.