Release creates no tag on first run

[brckd]

I use semantic release to automatically create releases on my repository. Lately however, the CI doesn't create a tag for the latest release. The tag is only added after re-running the CI. This leaves behind an older draft release without the tag and one valid release.

Releases:

Semantic release config:

export default {
  branches: ["main"],
  plugins: [
    "@semantic-release/commit-analyzer",
    "@semantic-release/release-notes-generator",
    "@semantic-release/github",
  ],
};

GitHub actions permissions:

permissions:
  contents: write
  issues: read

Logs:

Run npx semantic-release
npm warn exec The following package was not found and will be installed: semantic-release@24.2.2
[2:01:45 PM] [semantic-release] › ℹ  Running semantic-release version 24.2.2
[2:01:46 PM] [semantic-release] › ✔  Loaded plugin "verifyConditions" from "@semantic-release/github"
[2:01:46 PM] [semantic-release] › ✔  Loaded plugin "analyzeCommits" from "@semantic-release/commit-analyzer"
[2:01:46 PM] [semantic-release] › ✔  Loaded plugin "generateNotes" from "@semantic-release/release-notes-generator"
[2:01:46 PM] [semantic-release] › ✔  Loaded plugin "publish" from "@semantic-release/github"
[2:01:46 PM] [semantic-release] › ✔  Loaded plugin "addChannel" from "@semantic-release/github"
[2:01:46 PM] [semantic-release] › ✔  Loaded plugin "success" from "@semantic-release/github"
[2:01:46 PM] [semantic-release] › ✔  Loaded plugin "fail" from "@semantic-release/github"
[2:01:48 PM] [semantic-release] › ✔  Run automated release from branch main on repository git+https://github.com/brckd/pages.git
[2:01:48 PM] [semantic-release] › ✔  Allowed to push to the Git repository
[2:01:48 PM] [semantic-release] › ℹ  Start step "verifyConditions" of plugin "@semantic-release/github"
[2:01:48 PM] [semantic-release] [@semantic-release/github] › ℹ  Verify GitHub authentication (https://api.github.com/)
[2:01:48 PM] [semantic-release] › ✔  Completed step "verifyConditions" of plugin "@semantic-release/github"
[2:01:48 PM] [semantic-release] › ℹ  Found git tag v1.3.0 associated with version 1.3.0 on branch main
[2:01:48 PM] [semantic-release] › ℹ  Found 1 commits since last release
[2:01:48 PM] [semantic-release] › ℹ  Start step "analyzeCommits" of plugin "@semantic-release/commit-analyzer"
[2:01:48 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  Analyzing commit: feat: add new fonts and code block styling
[2:01:48 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  The release type for the commit is minor
[2:01:48 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  Analysis of 1 commits complete: minor release
[2:01:48 PM] [semantic-release] › ✔  Completed step "analyzeCommits" of plugin "@semantic-release/commit-analyzer"
[2:01:48 PM] [semantic-release] › ℹ  The next release version is 1.4.0
[2:01:48 PM] [semantic-release] › ℹ  Start step "generateNotes" of plugin "@semantic-release/release-notes-generator"
[2:01:48 PM] [semantic-release] › ✔  Completed step "generateNotes" of plugin "@semantic-release/release-notes-generator"
[2:01:50 PM] [semantic-release] › ✔  Created tag v1.4.0
[2:01:50 PM] [semantic-release] › ℹ  Start step "publish" of plugin "@semantic-release/github"
[2:01:51 PM] [semantic-release] [@semantic-release/github] › ℹ  Published GitHub release: https://github.com/brckd/pages/releases/tag/v1.4.0
[2:01:51 PM] [semantic-release] › ✔  Completed step "publish" of plugin "@semantic-release/github"
[2:01:51 PM] [semantic-release] › ℹ  Start step "success" of plugin "@semantic-release/github"
[2:01:53 PM] [semantic-release] › ✔  Completed step "success" of plugin "@semantic-release/github"
[2:01:53 PM] [semantic-release] › ✔  Published release 1.4.0 on default channel``` 

[babblebey]

Hey @brckd,

Removing the screenshot, but with the Logs and all, everything looks fine. 🤔

[brckd]

Yes, everything apart from the actual release and the missing tags is as expected.

[babblebey]

Very well, but I don't you get me.

I meant that everything looks alright, I checked the repository and everything looks in place.

Could you kindly attempt another release?? And this time, do not re-run the ci again after the failure you explained

[brckd]

I just tried doing it again, but it seems that I have fixed it accidentally. When I was trying to pull from origin, I got a Git warning that my tags were different from those on origin, so I decided to override mine. I created a new release and it worked flawlessly now.

I also changed the workflow permissions as recommended by the documentation, but that should be irrelevant.

permissions:
  contents: write
  issues: write
  pull-requests: write

[brckd]

Nevermind, the latest release has the same problem again. The workflow also looks fine.

I will try if pulling the tags regularly fixes the upcoming releases.

[babblebey]

Are you still experiencing this issue?

[brckd]

Yes, but I was able to mostly ignore it by deleting malformed pull requests. There still isn't any error in the logs though. Is there perhaps an option to enable more verbose logging?

[brckd]

The logs explicitly state Created tag ..., even though that's not what's happening :/

[travi]

Lately however

how recently did this start? could it possibly be timed with your switch to use bun/bunx instead of node/npx?

i dont see anything obviously wrong with your configuration. my best guess suggests that the git tag is failing to be pushed back to github and the tag on the github side is created as a result of the github release done through the github api instead. i dont understand why a second run would resolve this problem either as i would expect semantic-release to find the tag from github and determine that there is no remaining work to do.

i'm somewhat wondering if setup-bun changes how the git credentials are managed between the checkout step and the release step. i'm not a bun user, so i dont have specific experience there

[travi]

Is there perhaps an option to enable more verbose logging?

the debug flag can give additional output

[brckd]

Lately however

how recently did this start? could it possibly be timed with your switch to use bun/bunx instead of node/npx?

Yes, I recently switched to bun, but I also recently removed semantic-release/git alongside its permissions.

I'll try to figure it out using the debug flag!