Ci/publish workflow

[MarcelOlsen]

Summary by CodeRabbit

• Chores
  • Improved the publishing workflow to prevent republishing existing package versions.
  • Publishing and release steps now use the current version from the package information.
  • Added clearer messaging when a version is already published.
  • Removed automatic version bumping based on commit messages.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

Alright, chat, here's the rundown: The publish workflow for GitHub Actions just got absolutely refactored. No more automatic version bumping based on commit messages, no more git tagging, and no more using personal access tokens for checkout. Now, it just reads the version straight from package.json, checks if that exact version is already on NPM, and only publishes if it's not. It also updates the release creation logic and adds clear skip messaging when a version's already published. Clean and simple, baby!

Changes

File(s)	Change Summary
.github/workflows/publish.yml	Removed version bumping logic, git tagging, and commit parsing; improved NPM version checks; updated publish and release steps to use package info; added skip step for already published versions; removed use of personal access token for checkout.

Sequence Diagram(s)

sequenceDiagram
    participant Workflow
    participant package.json
    participant NPM Registry
    participant GitHub Releases

    Workflow->>package.json: Read name & version
    Workflow->>NPM Registry: Check if package exists
    alt Version already published
        Workflow->>Workflow: Output skip message
    else Version not published
        Workflow->>NPM Registry: Publish package
        Workflow->>GitHub Releases: Create release with tag/version
    end

Loading

Possibly related PRs

• Chore/clean git history #19: Both PRs overhaul .github/workflows/publish.yml but take opposite approaches to version bumping and tagging.
• 🔧 Fix GitHub Actions permissions and NPM publish workflow #20: Both PRs modify the publish workflow to enhance NPM publishing logic and conditional steps, but differ in token and permission handling.

Poem

🎉
No more bumps, no more tags,
Just read the version—no zigzags!
If it's published, we skip with glee,
If not, we ship it, easy as can be.
The workflow's clean, the code is tight,
Ship it live—feels just right!
🚀

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e25960e and 377d772.

📒 Files selected for processing (1)

• .github/workflows/publish.yml (2 hunks)

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.