Skip to content

fix: add publishConfig#7

Merged
petar-omni merged 1 commit intomainfrom
fix/cd
Jul 9, 2025
Merged

fix: add publishConfig#7
petar-omni merged 1 commit intomainfrom
fix/cd

Conversation

@petar-omni
Copy link
Contributor

No description provided.

@petar-omni petar-omni requested review from Philippoes and Copilot July 9, 2025 09:14
@changeset-bot
Copy link

changeset-bot bot commented Jul 9, 2025

⚠️ No Changeset found

Latest commit: d804bb9

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

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

Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

Adds publishConfig settings to the package.json to ensure the package is published publicly to the npm registry.

  • Introduces publishConfig with access: public
  • Specifies the npm registry URL for publishing

@petar-omni petar-omni merged commit 3e6a9df into main Jul 9, 2025
4 checks passed
@petar-omni petar-omni deleted the fix/cd branch July 9, 2025 09:17
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.

2 participants