fix: replace token from public to github

[SeUkKim]

Description

Closes: #XXXX

---

Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

I have...

• included the correct type prefix in the PR title, you can find examples of the prefixes below:
• confirmed ! in the type prefix if API or client breaking change
• targeted the correct branch
• provided a link to the relevant issue or specification
• reviewed "Files changed" and left comments if necessary
• included the necessary unit and integration tests
• updated the relevant documentation or specification, including comments for documenting Go code
• confirmed all CI checks have passed

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.

I have...

• confirmed the correct type prefix in the PR title
• confirmed all author checklist items have been addressed
• reviewed state machine logic, API design and naming, documentation is accurate, tests and test coverage

Summary by CodeRabbit

• Chores
  • Enhanced automated deployment by updating the authentication process, ensuring a smoother and more secure release workflow.

[coderabbitai]

Walkthrough

The GitHub Actions workflow file has been updated to adjust the authentication mechanism. Specifically, the token used in two push steps has been changed from secrets.PUBLISH_TOKEN to secrets.GITHUB_TOKEN. The affected steps are "Push files to move-natives" and "Push shared dynamic libraries to builder.js". The overall workflow structure remains unchanged.

Changes

File Path	Change Summary
.github/workflows/publish.yml	Replaced secrets.PUBLISH_TOKEN with secrets.GITHUB_TOKEN in the "Push files to move-natives" and "Push shared dynamic libraries to builder.js" steps.

Sequence Diagram(s)

sequenceDiagram
    participant WF as GitHub Workflow
    participant S as Secrets Store
    participant R as Repository
    WF->>S: Retrieve GITHUB_TOKEN
    WF->>R: Push "move-natives" files using GITHUB_TOKEN
    WF->>R: Push shared dynamic libraries using GITHUB_TOKEN

Loading

Suggested reviewers

• beer-1
• Vritra4

Poem

I'm a little rabbit, hopping with delight,
Adding new tokens to make our pushes just right.
From secrets old to secrets new we shift,
Helping workflows jump and swiftly lift.
In code and in hops, I cheer with a smile—
ASCII carrots abound in bunny style!
Hop on, happy code, with every file!

---

📜 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 e30084a and 977ec41.

📒 Files selected for processing (1)

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

🔇 Additional comments (2)

.github/workflows/publish.yml (2)

22-22: Secure Token Update for Push to move-natives
The environment variable for authentication in the "Push files to move-natives" step has been correctly updated to use ${{ secrets.GITHUB_TOKEN }}. This change improves security by ensuring that a more appropriately scoped token is used.

---

38-38: Secure Token Update for Push to builder.js
Similarly, the "Push shared dynamic libraries to builder.js" step now uses ${{ secrets.GITHUB_TOKEN }} for the TOKEN_GITHUB environment variable. This aligns with the security best practices expected in the CI/CD pipeline.

---

🪧 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.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate unit testing code.
  • @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.

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 docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @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.