Repository navigation
Add component tagging step to the release guide - #1133
Merged
Merged
Conversation
✅
|
| Descriptor | Linter | Files | Fixed | Errors | Max errors | Warnings | Elapsed time |
|---|---|---|---|---|---|---|---|
| ✅ ACTION | actionlint | 5 | 0 | 0 | 0.04s | ||
| ✅ JSON | jsonlint | 4 | 0 | 0 | 0.07s | ||
| ✅ JSON | prettier | 4 | 0 | 0 | 0.26s | ||
| ✅ JSON | v8r | 4 | 0 | 0 | 7.65s | ||
| ✅ MARKDOWN | markdownlint | 183 | 0 | 0 | 2.34s | ||
| ✅ MARKDOWN | markdown-table-formatter | 183 | 0 | 0 | 0.31s | ||
| ✅ REPOSITORY | betterleaks | yes | no | no | 0.6s | ||
| ✅ REPOSITORY | checkov | yes | no | no | 15.71s | ||
| ✅ REPOSITORY | git_diff | yes | no | no | 0.05s | ||
| ✅ REPOSITORY | secretlint | yes | no | no | 1.07s | ||
| ✅ REPOSITORY | trufflehog | yes | no | no | 2.43s | ||
| ✅ SPELL | codespell | 193 | 0 | 0 | 0.49s | ||
| lychee | 193 | 6 | 0 | 60.21s | |||
| ✅ YAML | prettier | 6 | 0 | 0 | 0.26s | ||
| ✅ YAML | v8r | 6 | 0 | 0 | 5.65s | ||
| ✅ YAML | yamllint | 6 | 0 | 0 | 0.47s |
Detailed Issues
⚠️ SPELL / lychee - 6 errors
📝 Summary
---------------------
🔍 Total.........1259
🔗 Unique.........933
✅ Successful....1120
⏳ Timeouts........24
🔀 Redirected.......7
👻 Excluded.......109
❓ Unknown..........0
🚫 Errors...........6
⛔ Unsupported......6
Errors in .claude/skills/security-advisory/reference/style.md
[ERROR] file://.claude/skills/guides/operations-guide/openstack/security-updates.md (at 189:3) | File not found. Check if file exists and path is correct
Errors in .claude/skills/security-advisory/SKILL.md
[TIMEOUT] https://api.launchpad.net/1.0/bugs/ (at 15:18) | Request timed out
[400] https://cveawg.mitre.org/api/cve/ (at 16:18) | Rejected status code: 400 Bad Request
[404] https://raw.githubusercontent.com/osism/ (at 17:18) | Rejected status code: 404 Not Found
[400] https://registry.osism.tech/service/token (at 18:19) | Rejected status code: 400 Bad Request
Errors in docs/appendix/security/ossa-2026-001.md
[TIMEOUT] https://bugs.launchpad.net/keystonemiddleware/+bug/2129018 (at 142:3) | Request timed out
Errors in docs/appendix/security/ossa-2026-005.md
[ERROR] https://security.openstack.org/ossa/OSSA-2026-005.html (at 123:3) | Connection closed before response completed
Errors in docs/appendix/security/ossa-2026-015.md
[TIMEOUT] https://bugs.launchpad.net/keystone/+bug/2148398 (at 194:3) | Request timed out
[TIMEOUT] https://bugs.launchpad.net/keystone/+bug/2148477 (at 195:3) | Request timed out
[TIMEOUT] https://bugs.launchpad.net/keystone/+bug/2149775 (at 196:3) | Request timed out
[TIMEOUT] https://bugs.launchpad.net/keystone/+bug/2149789 (at 197:3) | Request timed out
[TIMEOUT] https://bugs.launchpad.net/keystone/+bug/2150089 (at 198:3) | Request timed out
[TIMEOUT] https://bugs.launchpad.net/keystone/+bug/2150379 (at 199:3) | Request timed out
Errors in docs/appendix/security/ossa-2026-022.md
[TIMEOUT] https://bugs.launchpad.net/nova/+bug/2151252 (at 159:3) | Request timed out
Errors in docs/appendix/security/ossa-2026-032.md
[TIMEOUT] https://bugs.launchpad.net/neutron/+bug/2152113 (at 271:3) | Request timed out
Errors in docs/appendix/security/ossa-2026-034.md
[TIMEOUT] https://bugs.launchpad.net/designate/+bug/2142581 (at 179:5) | Request timed out
[TIMEOUT] https://bugs.launchpad.net/designate/+bug/2142581 (at 254:3) | Request timed out
[TIMEOUT] https://bugs.launchpad.net/designate/+bug/2160533 (at 186:5) | Request timed out
[TIMEOUT] https://bugs.launchpad.net/designate/+bug/2160533 (at 253:3) | Request timed out
Errors in docs/appendix/security/ossa-2026-038.md
[TIMEOUT] https://launchpad.net/bugs/2158998 (at 124:3) | Request timed out | Followed 1 redirect. Redirects: https://launchpad.net/bugs/2158998 --[303]--> https://bugs.launchpad.net/glance/+bug/2158998
[TIMEOUT] https://launchpad.net/bugs/2158999 (at 125:3) | Request timed out | Followed 1 redirect. Redirects: https://launchpad.net/bugs/2158999 --[303]--> https://bugs.launchpad.net/glance/+bug/2158999
[TIMEOUT] https://launchpad.net/bugs/2160020 (at 127:3) | Request timed out
[TIMEOUT] https://launchpad.net/bugs/2161330 (at 126:3) | Request timed out
Errors in docs/appendix/security/ossa-2026-039.md
[TIMEOUT] https://bugs.launchpad.net/octavia/+bug/2162101 (at 245:5) | Request timed out
[TIMEOUT] https://bugs.launchpad.net/octavia/+bug/2162103 (at 248:5) | Request timed out
[TIMEOUT] https://bugs.launchpad.net/octavia/+bug/2162103 (at 388:3) | Request timed out
Errors in docs/appendix/security/ossa-2026-045.md
[TIMEOUT] https://bugs.launchpad.net/cinder/+bug/2160671 (at 273:3) | Request timed out
Errors in docs/guides/developer-guide/style-guide.md
[ERROR] https://wiki.openstack.org/wiki/GitCommitMessages (at 79:1) | Network unreachable. Check internet connection or VPN settings
Errors in docs/guides/troubleshooting-guide/openstack.mdx
[TIMEOUT] https://bugs.launchpad.net/neutron/+bug/2111498 (at 268:13) | Request timed out
Errors in docs/release-notes/osism-9.md
[TIMEOUT] https://bugs.launchpad.net/kolla/+bug/2111620 (at 97:47) | Request timed out
Hint: Followed 7 redirects. You might want to consider replacing redirecting URLs with the resolved URLs. Use verbose mode (`-v`/`-vv`) to see redirection details.
See detailed reports in MegaLinter artifacts
Your project could benefit from a custom flavor, which would allow you to run only the linters you need, and thus improve runtime performances. (Skip this info by defining FLAVOR_SUGGESTIONS: false)
- Documentation: Custom Flavors
- Command:
npx mega-linter-runner@10.2.0 --custom-flavor-setup --custom-flavor-linters ACTION_ACTIONLINT,JSON_JSONLINT,JSON_V8R,JSON_PRETTIER,MARKDOWN_MARKDOWNLINT,MARKDOWN_MARKDOWN_TABLE_FORMATTER,REPOSITORY_CHECKOV,REPOSITORY_GIT_DIFF,REPOSITORY_BETTERLEAKS,REPOSITORY_SECRETLINT,REPOSITORY_TRUFFLEHOG,SPELL_LYCHEE,SPELL_CODESPELL,YAML_PRETTIER,YAML_YAMLLINT,YAML_V8R

Show us your support by starring ⭐ the repository
ideaship
marked this pull request as ready for review
November 11, 2026 21:06
ideaship
marked this pull request as draft
November 12, 2026 09:03
A release only contains component changes that are tagged: Renovate updates the pins in osism/release to published tags only, so a change merged on the default branch of defaults, the playbooks, a collection, python-osism or one of the tools pinned by python-osism is left out until its repository is tagged. The release guide did not mention this step. Add it as the first step of the checklist: every component that the release pins directly is tagged with the version of the release round, also without changes, so that all components of a release are tagged alike. The tools pinned by python-osism are tagged when they changed. check-versions.sh --release-tag of osism/release lists the components that lack the tag and the ones with untagged changes; create-tags.sh runs the same check. Intentional exceptions are accepted with --allow. The testing step now also says to tag the components that carry a fix. The following steps and their cross-references are renumbered. Assisted-by: Claude:claude-opus-5-5 Signed-off-by: Roger Luethi <luethi@osism.tech>
ideaship
force-pushed
the
release-components
branch
from
November 12, 2026 10:19
53b7def to
4950bd4
Compare
ideaship
marked this pull request as ready for review
November 12, 2026 13:32
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.
A release only contains component changes that are tagged. Renovate updates the pins in osism/release to published tags only, so a change merged on the default branch of defaults, the playbooks, a collection, python-osism or one of the tools pinned by python-osism is left out until its repository is tagged. The release guide did not mention this step.
check-versions.sh --release-tagof osism/release lists the components that lack the tag and the ones with untagged changes;create-tags.shruns the same check. Intentional exceptions are accepted with--allow.Depends on:
The new step links the README section that this PR adds, so it should be merged afterwards.
🤖 Generated with Claude Code