Conversation
Replace dual VERSION/VERSION_YAML files with single source of truth (version.yaml). Changes: - Consolidate versioning into single version.yaml file - Move version calculation logic into versioning.yml workflow - Update versioning.yml to: - Trigger only on PR merges to main (not direct commits) - Check for [skip-versioning] marker to prevent loops - Update version.yaml and bug.yml before committing - Handle tagging, releases, and floating tags (stable/latest) - Remove bump_version.sh script (logic now in workflow) - Update nspanel_esphome_version.yaml to include version.yaml Benefits: - Single file to maintain instead of two - Workflow controls entire release process - Cleaner separation of concerns - No tagging duplication
Contributor
📝 WalkthroughWalkthroughReworks CI versioning to compute and persist a CalVer (YYYY.M.seq) into Changes
Sequence Diagram(s)sequenceDiagram
participant Dev as Developer (PR)
participant GH as GitHub (Event)
participant Action as GitHub Actions
participant Repo as Repository
participant API as GitHub API
Dev->>GH: Merge PR into main
GH->>Action: Trigger workflow (pull_request: closed) or manual dispatch
Action->>Repo: Read `versioning/version.yaml`
Action->>Action: Check for `[skip-versioning]` and compute NEXT_VERSION (YYYY.M.SEQ)
alt not skipped
Action->>Repo: Fetch/rebase main, update `versioning/version.yaml` and templates
Action->>Repo: Commit changes with "[skip-versioning]"
Action->>API: Push commit and create/update tag `vNEXT_VERSION`
Action->>API: Optionally create GitHub Release and update stable/latest tags
end
API-->>Action: Return status
Action-->>Dev: Expose outputs (version, min versions)
Estimated code review effort🎯 4 (Complex) | ⏱️ ~45 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 6dd4d58d4e
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 4
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In @.github/workflows/versioning.yml:
- Around line 147-148: The yq reads for MIN_BLUEPRINT_VERSION and
MIN_TFT_VERSION are using the repository root path but the file lives under
esphome; update the yq commands that set MIN_BLUEPRINT_VERSION and
MIN_TFT_VERSION to point to esphome/nspanel_esphome_version.yaml (keep the same
yq expression '.substitutions.min_blueprint_version' and
'.substitutions.min_tft_version') so the workflow reads the correct file.
- Around line 170-173: The commit step "Commit version and template changes"
(id: commit) is guarded by the wrong event check; update its if condition to
include pull_request instead of push so merged PR runs don't skip it — e.g.,
change "if: github.event_name == 'workflow_dispatch' || (github.event_name ==
'push' && steps.skip_check.outputs.skip == 'false')" to include
github.event_name == 'pull_request' (or replace the push branch with
pull_request while keeping the skip_check guard) so steps.commit.outputs.version
is produced for downstream tag/release steps.
- Around line 162-168: Replace the literal "${VAR}" placeholders in the three yq
eval calls with yq's strenv() so the environment variables are read at runtime;
specifically update the expressions targeting '.body[3].attributes.placeholder',
'.body[4].attributes.placeholder', and '.body[5].attributes.placeholder' to use
strenv(MIN_TFT_VERSION), strenv(VERSION), and strenv(MIN_BLUEPRINT_VERSION)
respectively so yq interpolates the environment values instead of writing the
literal ${...} strings.
In `@versioning/version.yaml`:
- Around line 1-3: The YAML file lacks document start/end markers; open the file
containing the version: key (the version: 2026.2.12 entry) and add a document
start marker `---` before the first line and a document end marker `...` after
the last line so the file begins with `---` and ends with `...` to satisfy the
YAML document-start/document-end lint rules.
ℹ️ Review info
Configuration used: defaults
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (8)
.github/workflows/versioning.ymlesphome/nspanel_esphome_version.yamlversioning/.gitignoreversioning/DO_NOT_SET_VERSION_MANUALLYversioning/VERSIONversioning/VERSION_YAMLversioning/bump_version.shversioning/version.yaml
💤 Files with no reviewable changes (4)
- versioning/bump_version.sh
- versioning/VERSION
- versioning/DO_NOT_SET_VERSION_MANUALLY
- versioning/VERSION_YAML
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Ignore changes to versioning/version.yaml in the workflow.
Owner
Author
|
@codex review |
Contributor
There was a problem hiding this comment.
Actionable comments posted: 1
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (2)
.github/workflows/versioning.yml (2)
197-202:⚠️ Potential issue | 🔴 CriticalThe heredoc terminator is misaligned and will cause shell parsing failure—replace with printf.
The
cat << EOFblock uses a plain<<delimiter without the-flag, which requires the EOF terminator to start at column 0. However, the EOF at line 202 has leading whitespace, causing the shell to never recognize the terminator and hang indefinitely. The proposed printf solution eliminates this fragility.🔧 Proposed fix
else # Manual dispatch or PR info unavailable - simpler message - cat > tag_message.txt << EOF - # v${NEW_VERSION} - Manual tag update - - Tag updated via manual workflow dispatch. - EOF + { + printf '# v%s - Manual tag update\n\n' "$NEW_VERSION" + printf '%s\n' 'Tag updated via manual workflow dispatch.' + } > tag_message.txt fi🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In @.github/workflows/versioning.yml around lines 197 - 202, The heredoc writing to tag_message.txt using "cat > tag_message.txt << EOF" has a misaligned EOF terminator and can hang; replace the heredoc with a safe printf-based write that emits the same multiline contents (including the v${NEW_VERSION} header and the "Tag updated via manual workflow dispatch." body) into tag_message.txt, ensuring proper newlines and quoting so the NEW_VERSION variable expands correctly.
46-50:⚠️ Potential issue | 🟠 MajorUse
HEAD:mainto push deterministically in CI context.The workflow uses
git push origin mainwithout a localmainbranch explicitly set (checkout lacksref: main). In CI environments with potential detached HEAD states,git push origin HEAD:mainis more reliable—it explicitly pushes the current HEAD regardless of branch state.🔧 Proposed fix
- name: Checkout code uses: actions/checkout@v4 with: fetch-depth: 0 + ref: main ... - name: Push changes if: github.event_name == 'workflow_dispatch' || (github.event_name == 'pull_request' && steps.skip_check.outputs.skip == 'false') env: GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} run: | - git push origin main + git push origin HEAD:mainAlso applies to: 225, 268, 292
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In @.github/workflows/versioning.yml around lines 46 - 50, The checkout step uses "uses: actions/checkout@v4" without pinning a branch and the workflow later runs "git push origin main" which can fail in detached-HEAD CI runs; update the checkout step to include "ref: main" or (preferable) change all push commands that currently run "git push origin main" to "git push origin HEAD:main" so the current commit is pushed deterministically; update every occurrence of the push command (the occurrences flagged around the later push steps) and keep the checkout action as-is except add ref if you prefer explicit branch checkout.
🧹 Nitpick comments (1)
.github/workflows/versioning.yml (1)
120-130: Remove stray##endif`` markers from shell comments.These markers look accidental and reduce readability in the version calculation block.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In @.github/workflows/versioning.yml around lines 120 - 130, Remove the stray "# `#endif`" tokens embedded in comments around the version calculation block; edit the lines that set CURRENT_MONTH, the comment after it, and the comment after NEXT_SEQ so they are regular shell comments (e.g., "Avoid leading zero for the month" and "Reset sequence for a new month") without the "# `#endif`" fragments; ensure variables CURRENT_MONTH, CURRENT_SEQ, CURRENT_VERSION, VERSION_YEAR, VERSION_MONTH, and NEXT_SEQ remain unchanged and logic in the if block is preserved.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In @.github/workflows/versioning.yml:
- Around line 2-7: Update the top comment block to accurately reflect the
workflow triggers: replace the incorrect “Pushing to main” description with
wording that states the workflow runs on merged PR close (pull_request with
types: closed/merged) and via manual dispatch (workflow_dispatch); mention that
it still skips execution when the commit message contains [skip-versioning] to
avoid loops and reference the workflow trigger keys 'on:', 'pull_request', and
'workflow_dispatch' so operators can quickly map the comment to the actual
triggers.
---
Outside diff comments:
In @.github/workflows/versioning.yml:
- Around line 197-202: The heredoc writing to tag_message.txt using "cat >
tag_message.txt << EOF" has a misaligned EOF terminator and can hang; replace
the heredoc with a safe printf-based write that emits the same multiline
contents (including the v${NEW_VERSION} header and the "Tag updated via manual
workflow dispatch." body) into tag_message.txt, ensuring proper newlines and
quoting so the NEW_VERSION variable expands correctly.
- Around line 46-50: The checkout step uses "uses: actions/checkout@v4" without
pinning a branch and the workflow later runs "git push origin main" which can
fail in detached-HEAD CI runs; update the checkout step to include "ref: main"
or (preferable) change all push commands that currently run "git push origin
main" to "git push origin HEAD:main" so the current commit is pushed
deterministically; update every occurrence of the push command (the occurrences
flagged around the later push steps) and keep the checkout action as-is except
add ref if you prefer explicit branch checkout.
---
Nitpick comments:
In @.github/workflows/versioning.yml:
- Around line 120-130: Remove the stray "# `#endif`" tokens embedded in comments
around the version calculation block; edit the lines that set CURRENT_MONTH, the
comment after it, and the comment after NEXT_SEQ so they are regular shell
comments (e.g., "Avoid leading zero for the month" and "Reset sequence for a new
month") without the "# `#endif`" fragments; ensure variables CURRENT_MONTH,
CURRENT_SEQ, CURRENT_VERSION, VERSION_YEAR, VERSION_MONTH, and NEXT_SEQ remain
unchanged and logic in the if block is preserved.
ℹ️ Review info
Configuration used: defaults
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (2)
.github/workflows/versioning.ymlversioning/version.yaml
🚧 Files skipped from review as they are similar to previous changes (1)
- versioning/version.yaml
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: b27c0b3f66
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Contributor
There was a problem hiding this comment.
🧹 Nitpick comments (1)
.github/workflows/versioning.yml (1)
120-130: Clean up the##endif`` comment artifacts.The comments on lines 120 and 130 contain
##endif`` which appears to be a copy-paste artifact or leftover from a different context. These should be simplified to standard comments.✨ Suggested cleanup
- CURRENT_MONTH=$(date +%-m) # `#endif` Avoid leading zero for the month + CURRENT_MONTH=$(date +%-m) # Avoid leading zero for the month CURRENT_SEQ=$(echo "$CURRENT_VERSION" | awk -F. '{print $3}') ... if [[ "$CURRENT_YEAR" == "$VERSION_YEAR" && "$CURRENT_MONTH" == "$VERSION_MONTH" ]]; then NEXT_SEQ=$((CURRENT_SEQ + 1)) else - NEXT_SEQ=1 # `#endif` Reset sequence for a new month + NEXT_SEQ=1 # Reset sequence for a new month fi🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In @.github/workflows/versioning.yml around lines 120 - 130, Remove the stray "# `#endif`" artifacts in the versioning logic comments and replace them with clear standard comments: update the comment after CURRENT_MONTH to something like "Avoid leading zero for the month" and change the comment after NEXT_SEQ=1 to "Reset sequence for a new month"; ensure you edit lines around the variables CURRENT_MONTH, CURRENT_SEQ, VERSION_YEAR, VERSION_MONTH and NEXT_SEQ in the versioning workflow so only meaningful explanatory comments remain.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Nitpick comments:
In @.github/workflows/versioning.yml:
- Around line 120-130: Remove the stray "# `#endif`" artifacts in the versioning
logic comments and replace them with clear standard comments: update the comment
after CURRENT_MONTH to something like "Avoid leading zero for the month" and
change the comment after NEXT_SEQ=1 to "Reset sequence for a new month"; ensure
you edit lines around the variables CURRENT_MONTH, CURRENT_SEQ, VERSION_YEAR,
VERSION_MONTH and NEXT_SEQ in the versioning workflow so only meaningful
explanatory comments remain.
Owner
Author
|
@codex review |
Contributor
There was a problem hiding this comment.
Actionable comments posted: 3
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In @.github/workflows/versioning.yml:
- Around line 99-110: The workflow currently lets manual workflow_dispatch runs
perform the full bump/commit/tag/release flow because multiple steps (e.g., the
steps with ids current_version and next_version and the bump/commit/tag/release
steps referenced in the comment) use a condition that permits workflow_dispatch;
change those steps' if conditions so full release actions only run when NOT a
manual dispatch OR when an explicit allow flag is set (e.g., if:
github.event_name != 'workflow_dispatch' || inputs.allow_release == 'true' or
similar), and keep the existing read-only floats/maintenance steps available for
workflow_dispatch without triggering bump/commit/tag/release; apply this guard
to all bump/commit/tag/release steps to ensure manual runs can perform
floating-tag maintenance only.
- Around line 209-215: The "Push changes" step currently runs git push origin
HEAD:main which will fail if origin/main advanced during the job; update the
step to fetch origin/main and rebase local HEAD onto it before pushing (e.g.,
run git fetch origin main && git rebase origin/main) and then push, or if you
must force use git push --force-with-lease to avoid clobbering concurrent
changes; modify the command that currently uses "git push origin HEAD:main" to
perform a safe fetch+rebase or use --force-with-lease so the push won't be
rejected when main has advanced.
- Around line 164-170: The yq assignments for .body[3].attributes.placeholder,
.body[4].attributes.placeholder, and .body[5].attributes.placeholder are using
the unsafe pattern `= strenv(VAR) | "e.g., " + .` which pipes the whole document
into concatenation and fails; update each yq eval to perform the concatenation
on the right-hand side so the placeholder is assigned the string "e.g., " +
value of the environment variable (use MIN_TFT_VERSION for the first, VERSION
for the second, and MIN_BLUEPRINT_VERSION for the third) when writing to
.github/ISSUE_TEMPLATE/bug.yml, ensuring the assignment expression is `= "e.g.,
" + strenv(VARIABLE)` rather than piping the document into the concatenation.
ℹ️ Review info
Configuration used: defaults
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (2)
.github/workflows/versioning.ymlversioning/version.yaml
🚧 Files skipped from review as they are similar to previous changes (1)
- versioning/version.yaml
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 2bc4550a1c
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Contributor
There was a problem hiding this comment.
♻️ Duplicate comments (1)
.github/workflows/versioning.yml (1)
205-210:⚠️ Potential issue | 🟡 MinorPush step remains vulnerable to race conditions.
The push at line 210 can fail if
mainadvances after the early rebase (line 100). While concurrency control reduces risk from parallel workflow runs, direct pushes tomainduring workflow execution would cause a failure.Consider adding fetch/rebase immediately before the push, or use
--force-with-leasewith appropriate safeguards:🔧 Proposed hardening
- name: Push changes to main if: steps.skip_check.outputs.skip == 'false' env: GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} run: | + # Rebase in case main advanced during workflow execution + git fetch origin main + git rebase origin/main || { + echo "Rebase failed - main has diverged" + exit 1 + } git push origin HEAD:main🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In @.github/workflows/versioning.yml around lines 205 - 210, The push step "Push changes to main" currently does a direct git push (git push origin HEAD:main) which can fail due to race conditions if main advanced; update the step to fetch the remote and rebase/merge the latest main before pushing or change the push to use a safe force with lease (e.g., use git fetch origin main then git rebase origin/main or git merge --ff-only origin/main, and if necessary push with --force-with-lease) to prevent clobbering concurrent updates while avoiding race failures.
🧹 Nitpick comments (2)
.github/workflows/versioning.yml (2)
106-113: Consider handling missing or null version.If
version.yamldoesn't exist or the.versionkey is missing,yq eval '.version'returnsnull. The regex validation would catch this, but an explicit existence check would provide a clearer error message.🔧 Suggested improvement
# Read version AFTER rebase to avoid race conditions CURRENT_VERSION=$(yq eval '.version' ./versioning/version.yaml) + if [[ -z "$CURRENT_VERSION" || "$CURRENT_VERSION" == "null" ]]; then + echo "Error: Could not read version from versioning/version.yaml" + exit 1 + fi # Validate the current version format (CalVer: YYYY.M.seq)🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In @.github/workflows/versioning.yml around lines 106 - 113, Check for a missing or null version before applying the regex: after reading CURRENT_VERSION via yq eval '.version' (used in the workflow), add an explicit check that CURRENT_VERSION is non-empty and not "null" and emit a clear error message (e.g., "Error: version not found in versioning/version.yaml") and exit non-zero if it is missing; then proceed with the existing regex validation of CURRENT_VERSION.
138-139: Consider usingstrenv()for version strings.Using
env()works for CalVer versions, butstrenv()explicitly treats the value as a string, avoiding any edge cases where YAML parsing could interpret the version unexpectedly.🔧 Suggested change
- yq eval '.version = env(NEW_VERSION)' -i ./versioning/version.yaml + yq eval '.version = strenv(NEW_VERSION)' -i ./versioning/version.yaml🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In @.github/workflows/versioning.yml around lines 138 - 139, The yq expression uses env(NEW_VERSION) which can let YAML parser treat the version non-string; change the assignment to use strenv(NEW_VERSION) so the version is injected explicitly as a string. Update the command that runs yq (the line containing ".version = env(NEW_VERSION)" and the yq invocation) to replace env(...) with strenv(...) to ensure CalVer or other versions are always written as strings into version.yaml.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Duplicate comments:
In @.github/workflows/versioning.yml:
- Around line 205-210: The push step "Push changes to main" currently does a
direct git push (git push origin HEAD:main) which can fail due to race
conditions if main advanced; update the step to fetch the remote and
rebase/merge the latest main before pushing or change the push to use a safe
force with lease (e.g., use git fetch origin main then git rebase origin/main or
git merge --ff-only origin/main, and if necessary push with --force-with-lease)
to prevent clobbering concurrent updates while avoiding race failures.
---
Nitpick comments:
In @.github/workflows/versioning.yml:
- Around line 106-113: Check for a missing or null version before applying the
regex: after reading CURRENT_VERSION via yq eval '.version' (used in the
workflow), add an explicit check that CURRENT_VERSION is non-empty and not
"null" and emit a clear error message (e.g., "Error: version not found in
versioning/version.yaml") and exit non-zero if it is missing; then proceed with
the existing regex validation of CURRENT_VERSION.
- Around line 138-139: The yq expression uses env(NEW_VERSION) which can let
YAML parser treat the version non-string; change the assignment to use
strenv(NEW_VERSION) so the version is injected explicitly as a string. Update
the command that runs yq (the line containing ".version = env(NEW_VERSION)" and
the yq invocation) to replace env(...) with strenv(...) to ensure CalVer or
other versions are always written as strings into version.yaml.
Owner
Author
|
@codex review |
Contributor
|
✅ Actions performedReview triggered.
|
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 83abca7c49
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Contributor
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In @.github/workflows/versioning.yml:
- Line 39: The workflow currently pins third-party actions with mutable tags
(actions/checkout@v6, mikefarah/yq@v4.43.1, actions/github-script@v7,
softprops/action-gh-release@v2); replace each of those references with the
corresponding repository commit SHA (the 40-character immutable commit hash) for
the exact tag/version you intend to use—fetch the commit SHA from the action's
GitHub repo (releases/tags or the tag's commit) and update the workflow
references so each action entry uses the full 40-character SHA instead of the
floating tag.
- Around line 43-52: The current skip check step (name "Check for skip marker",
id skip_check) is reading the merge commit message and can be triggered by PR
metadata; change it to branch behavior on GITHUB_EVENT_NAME: when
GITHUB_EVENT_NAME == "pull_request" read the PR title/body from the GitHub event
file (GITHUB_EVENT_PATH) and only set skip if the PR title/body contains
"[skip-versioning]", and when GITHUB_EVENT_NAME == "push" (merged branch)
examine the last non-merge commit message (use git log --no-merges -1
--pretty=%B) for the marker; update the logic that echoes
"skip=true"/"skip=false" accordingly so PR metadata no longer unintentionally
disables releases.
Owner
Author
|
@coderabbitai resume |
Contributor
✅ Actions performedReviews resumed. |
edwardtfn
changed the title
This was referenced Mar 30, 2026
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.
Replace dual VERSION/VERSION_YAML files with single source of truth (version.yaml).
Changes:
Benefits:
Coverage:
[skip-versioning]markerversion.yamlYYYY.M.seq— increments seq or resets for new monthversion.yamlusing yq[skip-versioning]v2026.2.4)softprops/action-gh-releasestabletag (floating)stabletag to the new versionlatesttag (floating)latesttag to the new versionSummary by CodeRabbit
Chores
Documentation