Update version to 0.0.1-beta.20 in package.json and package-lock.json…

[fcarrero]

…; change npm registry to public and remove GitHub Packages workflow configuration.

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! 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 focuses on preparing the package for public distribution by updating its version, simplifying its name, and reconfiguring the publishing settings to target the public npm registry. These changes ensure that the package can be easily accessed and utilized by a broader audience through standard npm channels.

Highlights

• Version Update: The package version has been updated from 0.0.1-beta.19 to 0.0.1-beta.20 in both package.json and package-lock.json.
• Package Name Change: The package name has been changed from @conekta/conekta-elements-react-native to conekta-elements-react-native.
• NPM Registry Configuration: The publishConfig in package.json has been updated to use the public npm registry (https://registry.npmjs.org) and set the package access to public, removing the previous GitHub Packages registry.

🧠 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.

Changelog

• package-lock.json
  • Updated package version to 0.0.1-beta.20
  • Changed package name from @conekta/conekta-elements-react-native to conekta-elements-react-native
• package.json
  • Updated package version to 0.0.1-beta.20
  • Changed package name from @conekta/conekta-elements-react-native to conekta-elements-react-native
  • Modified publishConfig to use the public npm registry and set access to public

Ignored Files

• Ignored by pattern: .github/workflows/** (1)
  • .github/workflows/publish-npm.yml

Activity

• No human activity has been recorded on this pull request yet.

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. ↩

[gemini-code-assist]

Code Review

This pull request updates the package version and name in package.json and package-lock.json, and modifies the publishConfig to switch from GitHub Packages to the public npm registry. The changes correctly implement the move to a public registry. However, I've suggested a more significant version bump to better communicate the breaking change of renaming the package from a scoped to an unscoped name. This will help consumers of the package understand the impact of this update.

_{Note: Security Review has been skipped due to the limited scope of the PR.}

[Copilot]

Pull request overview

Updates the library’s npm publishing setup to move off GitHub Packages and publish a new beta version to the public npm registry.

Changes:

• Bumps version from 0.0.1-beta.19 to 0.0.1-beta.20.
• Renames the npm package from @conekta/conekta-elements-react-native to conekta-elements-react-native and updates publishConfig to publish to registry.npmjs.org.
• Updates the GitHub Actions release workflow to publish to npm using NPM_TOKEN instead of GITHUB_TOKEN.

Reviewed changes

Copilot reviewed 2 out of 3 changed files in this pull request and generated 2 comments.

File	Description
package.json	Updates package name/version and publish configuration for public npm publishing.
package-lock.json	Aligns lockfile metadata (name/version) with the new package identity.
.github/workflows/publish-npm.yml	Switches CI publishing target from GitHub Packages to npm registry and updates auth.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.