-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
generate-changelog.sh
script in meta-dts doesn't work correctly when used according to release process
#1173
Comments
I suggest that we do the following:
The workflow above can be scripted. |
It can't be scripted as pushing tag will start release workflow. Changelog needs to be reviewed before that and maybe manually changed. |
There is still Dasharo/meta-dts#207 (review) diff --git a/CHANGELOG.md b/CHANGELOG.md
index 4b0fa16a2d27..45c341d4c87b 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -4,6 +4,14 @@ All notable changes to this project will be documented in this file.
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/).
+## [2.1.2] - 2024-12-18
+
+### Changed
+- .github/workflows/test.yml: Improve test workflow (#200)
+- scripts/generate-changelog.sh: Fix arguments
+- wip
+
+
## [2.1.1] - 2024-12-13
### Added Doesn't create links:
Those would need to be added manually, by script (e.g. sed to insert after/before some line) or remove links completely. |
The reason why the links aren't getting updated is that we're using the |
Or add them manually or in script: PREV_DTS_VER="2.1.3"
CUR_DTS_VER="2.1.4"
# escape characters interpreted by sed e.g. "[1.2.3]:" -> "\[1\.2\.3\]:"
SED_MATCH=$(printf '%s\n' "[$PREV_DTS_VER]:" | sed -e 's/[]\/$*.^[]/\\&/g')
sed -i "\|^$SED_MATCH|i [$CUR_DTS_VER]: https://github.com/Dasharo/meta-dts/compare/v$PREV_DTS_VER..v$CUR_DTS_VER" CHANGELOG.md |
Component
Dasharo Tools Suite
Device
other
Dasharo version
No response
Dasharo Tools Suite version
v2.1.0
Test case ID
No response
Brief summary
Script doesn't generate changelog for unreleased (before putting tag) changes
How reproducible
100%
How to reproduce
Follow https://docs.zarhus.com/development-process/standard-release-process/#process-steps
Expected behavior
Script generates changes for version either in
dts-distro.conf
or takes version from argumentActual behavior
Script updates changelog for
2.1.0
insteadScreenshots
No response
Additional context
No response
Solutions you've tried
@PLangowski
The text was updated successfully, but these errors were encountered: