chore: call npm whoami and npm config get registry during publish

[MantisClone]

Towards #29

Changes

• call npm whoami and npm config get registry during publish

Summary by CodeRabbit

• Chores
  • Improved npm publish workflow by adding checks for user and registry configurations before performing a dry run publish.

[coderabbitai]

Walkthrough

The updates to the npm publish workflow in .github/workflows/npm-publish.yaml introduce commands to verify the npm user and registry configuration before executing a dry run publish. This enhancement aims to ensure that the correct user and registry settings are in place, thereby increasing the robustness and reliability of the publication process.

Changes

File	Change Summary
.github/workflows/npm-publish.yaml	Added commands to check npm user and registry configuration before performing a dry run publish. This ensures correct settings before publication.

Sequence Diagram(s)

sequenceDiagram
    participant Workflow as GitHub Actions Workflow
    participant NPM as NPM Registry
    participant User as NPM User

    Workflow->>User: Check npm user configuration
    User-->>Workflow: Configuration Details
    Workflow->>NPM: Check npm registry configuration
    NPM-->>Workflow: Registry Details
    Workflow->>Workflow: Verify configurations
    Workflow->>NPM: Perform dry run publish
    NPM-->>Workflow: Dry run results

Loading

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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 as 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 resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration 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.

[coderabbitai]

Actionable comments posted: 1

Review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE

Commits

Files that changed from the base of the PR and between b0a6062 and f8ad592.

Files selected for processing (1)

• .github/workflows/npm-publish.yaml (1 hunks)

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE

Commits

Files that changed from the base of the PR and between f8ad592 and f335da9.

Files selected for processing (1)

• .github/workflows/npm-publish.yaml (1 hunks)

Additional comments not posted (1)

.github/workflows/npm-publish.yaml (1)

50-52: Review of added npm commands

The integration of npm whoami and npm config get registry commands with error handling is well done. These commands enhance the robustness of the publish process by ensuring the npm user and registry configuration are correct before proceeding with the publish operation. The use of conditional exits (exit 1) ensures that the workflow will halt if these commands fail, which is a critical safeguard.

This implementation addresses the previous comment by ensuring that the workflow fails gracefully if the environment is not correctly configured. Thus, the changes are appropriate and improve the reliability of the deployment process.