Skip to content

Feature/update multipublish configuration#196

Merged
stephansama merged 2 commits into
mainfrom
feature/update-multipublish-configuration
Jan 15, 2026
Merged

Feature/update multipublish configuration#196
stephansama merged 2 commits into
mainfrom
feature/update-multipublish-configuration

Conversation

@stephansama
Copy link
Copy Markdown
Owner

Checklist

  • Latest changes from main have been merged
  • Conflicts have been resolved
  • The branch is pointing to main
  • Eslint hasn't reported any issues.
  • All unit tests pass

@changeset-bot
Copy link
Copy Markdown

changeset-bot Bot commented Jan 15, 2026

🦋 Changeset detected

Latest commit: 82acf08

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
@stephansama/multipublish Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@vercel
Copy link
Copy Markdown

vercel Bot commented Jan 15, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Review Updated (UTC)
packages Building Building Preview, Comment Jan 15, 2026 8:11am

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Jan 15, 2026

Caution

Review failed

The pull request is closed.

📝 Walkthrough

Summary by CodeRabbit

  • Chores
    • Updated publishing configuration for improved package distribution across multiple registries.

✏️ Tip: You can customize this high-level summary in your review settings.

Walkthrough

Updates the multipublish configuration to add JSR defaultExclude pattern and corrects the npm registry URL format by adding the protocol scheme and trailing slash. A corresponding changeset file marks this as a patch release.

Changes

Cohort / File(s) Summary
Changeset metadata
.changeset/some-words-rush.md
New changeset declaring patch release for "@stephansama/multipublish" with update message
Multipublish configuration
.config/.multipublishrc.json
JSR block: added defaultExclude: ["!config"] to exclude config directory; npm block: corrected registry URL from "npm.pkg.github.com" to "https://npm.pkg.github.com/"

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

Poem

🐰 A config update hops into place,
With JSR defaults set with grace,
The npm registry now has scheme,
A patch release fulfills the dream! 📦✨

✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch feature/update-multipublish-configuration


📜 Recent review details

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Disabled knowledge base sources:

  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between b3a6e7b and 82acf08.

📒 Files selected for processing (2)
  • .changeset/some-words-rush.md
  • .config/.multipublishrc.json

✏️ Tip: You can disable this entire section by setting review_details to false in your review settings.


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

Comment @coderabbitai help to get the list of available commands and usage tips.

@stephansama stephansama merged commit a4521b3 into main Jan 15, 2026
6 of 8 checks passed
@gemini-code-assist
Copy link
Copy Markdown

Summary of Changes

Hello @stephansama, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request refines the publishing configuration for the @stephansama/multipublish package. It introduces a new changeset to mark a patch update, adjusts the JSR publishing rules to ensure specific configuration files are included, and corrects the URL for the NPM package registry.

Highlights

  • Changeset Added: A new changeset file (.changeset/some-words-rush.md) has been added, signaling a patch version update for the @stephansama/multipublish package, with the description "update multipublish configuration".
  • JSR Configuration Update: The .config/.multipublishrc.json file now includes a "defaultExclude": ["!config"] entry within the jsr publishing configuration. This change likely ensures that files within the config directory are explicitly included when publishing to JSR.
  • NPM Registry URL Correction: The registry URL for npm publishing in .config/.multipublishrc.json has been updated from "npm.pkg.github.com" to the full URL "https://npm.pkg.github.com/".

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@codecov
Copy link
Copy Markdown

codecov Bot commented Jan 15, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ All tests successful. No failed tests found.

📢 Thoughts on this report? Let us know!

Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request updates the multipublish configuration. The changes in .config/.multipublishrc.json are twofold:

  • The npm platform's registry URL for GitHub Packages is corrected by adding the https:// protocol. This fixes a critical bug where an invalid URL would cause a crash.
  • A defaultExclude setting is added for the jsr platform. This is a configuration to ensure the config directory is included when publishing to JSR, likely by overriding a default exclusion rule.

A corresponding changeset file is included to mark this as a patch update. The changes are logical and correct. After a thorough review, I have no suggestions for improvement.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant