Skip to content

feat: add semantic release configuration and GitHub Actions workflow - #18

Merged
JMauclair merged 1 commit into
mainfrom
implement/semantic_release
Nov 28, 2025
Merged

feat: add semantic release configuration and GitHub Actions workflow#18
JMauclair merged 1 commit into
mainfrom
implement/semantic_release

Conversation

@JMauclair

Copy link
Copy Markdown
Contributor

No description provided.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

ℹ️ 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".

Comment on lines +25 to +29
- name: Run Semantic Release
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
run: npx semantic-release

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge GitHub release job missing Gitea token required by config

The GitHub Actions release job only exports GITHUB_TOKEN and NPM_TOKEN (lines 25‑28), but .releaserc.json enables the Gitea publisher (@saithodev/semantic-release-gitea, lines 19‑25). When this workflow runs, semantic-release will load that plugin and fail early because no GITEA_TOKEN is present, so the release job cannot succeed. Add the GITEA_TOKEN secret to the job env or conditionally disable the Gitea plugin when running on GitHub.

Useful? React with 👍 / 👎.

Comment on lines +25 to +32
- name: Run Semantic Release
env:
GITEA_TOKEN: ${{ secrets.GITEATOKEN }} # IMPORTANT
GIT_AUTHOR_NAME: "Semantic Release Bot"
GIT_AUTHOR_EMAIL: "bot@stralya.com"
GIT_COMMITTER_NAME: "Semantic Release Bot"
GIT_COMMITTER_EMAIL: "bot@stralya.com"
run: |

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Gitea release job lacks GitHub token for configured plugin

The Gitea workflow sets up only GITEA_TOKEN and git author info (lines 25‑32), yet .releaserc.json also includes the GitHub publisher @semantic-release/github (lines 19‑20). Running semantic-release here will call the GitHub plugin, which requires GITHUB_TOKEN/GH_TOKEN; without it the job will error before publishing. Provide a GitHub token in this workflow or gate that plugin when running on Gitea.

Useful? React with 👍 / 👎.

@JMauclair
JMauclair merged commit 6a64d28 into main Nov 28, 2025
1 check passed
@JMauclair
JMauclair deleted the implement/semantic_release branch November 28, 2025 10:22
@github-actions

Copy link
Copy Markdown

🎉 This PR is included in version 1.0.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant