-
Hi,
I am using semantic release to publish my package, which means that at build time my package version is always the same (`0.0.0-dev`).
Would one be able to integrate this easily with semant…
-
With https://github.com/open-telemetry/semantic-conventions/pull/1188 a semantic convention will be introduced for profiles. These new attributes should be used as replacement for `message Location.ty…
-
## :rotating_light: The automated release from the `main` branch failed. :rotating_light:
I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug…
-
## :rotating_light: The automated release from the `main` branch failed. :rotating_light:
I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug…
-
## :rotating_light: The automated release from the `main` branch failed. :rotating_light:
I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug…
-
It is [a common practice](https://stackoverflow.com/questions/21639437/git-flow-release-branches-and-tags-with-or-without-v-prefix) to tag releases as `v1.2.3` for version `1.2.3`.
From [semver.org…
-
There's confusion between the semantic version defined in the generated header and `g_release`, which is a FRACTINT-ism. The variable `g_release` should only be used for writing out the `release=` va…
-
### Current Behavior
Bumping past version 1.115.5 causes the `use-did-finish-ssr` module to no longer resolve. When adding the dependency manually, after app bootup I get the following: `TypeError: C…
-
## The problem
Hello , i have an issue with the incrementation of the patch version from pre-release to release using azure devops pipeline
## Expected behavior
v0.3.0-rc.1 -> v0.3.0 -> (push fi…
-
### New feature motivation
the conversation in https://github.com/semantic-release/semantic-release/issues/2503 resulted in the realization that the true desire is support for an additional workflo…
travi updated
1 month ago