Skip to content

move the development tag to the current main commit - #73

Merged
jkandasa merged 1 commit into
mycontroller-org:mainfrom
jkandasa:fix-development-tag-and-actions
Sep 18, 2026
Merged

jkandasa merged 1 commit into
mycontroller-org:mainfrom
jkandasa:fix-development-tag-and-actions

Conversation

@jkandasa

Copy link
Copy Markdown
Member

Summary

The last successful release run published the development release at e9563477 (#72), but refs/tags/development stayed on 87029226 (#70). GitHub ignores target_commitish when the tag already exists, so the releases page still shows the old commit.

  • Delete the development release and the tag ref before creating the new one.
  • Force-update refs/tags/development to ${{ github.sha }} after publish.

Also bump actions/upload-artifact and download-artifact from v4 → v6. The run warnings were those actions still targeting Node 20 on a Node 24 runner (punycode / Buffer() deprecations are inside those actions).

Test plan

target_commitish updates the release metadata but leaves the
git tag on the old SHA. Delete the tag ref, then force it to
github.sha. Also bump artifact actions to v6 to drop Node 20.
@jkandasa
jkandasa merged commit 99fca17 into mycontroller-org:main Sep 18, 2026
1 check passed
@jkandasa
jkandasa deleted the fix-development-tag-and-actions branch September 18, 2026 01:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant