Skip to content

Conversation

@GarthDB
Copy link
Member

@GarthDB GarthDB commented May 26, 2025

snyk-top-banner

Snyk has created this PR to upgrade @spectrum-web-components/textfield from 0.48.1 to 0.49.0.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 4 versions ahead of your current version.

  • The recommended version was released 7 months ago.

Release notes
Package name: @spectrum-web-components/textfield
  • 0.49.0 - 2024-10-15
  • 0.49.0-beta.2 - 2024-10-15
  • 0.49.0-beta.1 - 2024-10-14
  • 0.49.0-beta.0 - 2024-10-01
  • 0.48.1 - 2024-10-01
from @spectrum-web-components/textfield GitHub release notes

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

Snyk has created this PR to upgrade @spectrum-web-components/textfield from 0.48.1 to 0.49.0.

See this package in npm:
@spectrum-web-components/textfield

See this project in Snyk:
https://app.snyk.io/org/garthdb/project/5f85f718-4a4d-4dbb-b762-3b6dad7b9f59?utm_source=github&utm_medium=referral&page=upgrade-pr
@changeset-bot
Copy link

changeset-bot bot commented May 26, 2025

⚠️ No Changeset found

Latest commit: 87316ab

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

@GarthDB
Copy link
Member Author

GarthDB commented May 26, 2025

Run report for 87316abf

Total time: 5.7s | Comparison time: 3.5s | Estimated loss: 2.3s (39.2% slower)

Action Time Status Info
🟩 SyncWorkspace 6ms Passed
🟩 SyncProject(visualizer) 0.3ms Passed
⬛️ SetupToolchain(node:~20.12) 1.2s Skipped
🟥 InstallWorkspaceDeps(node:~20.12) 2.3s Aborted
Touched files
docs/visualizer/package.json

@GarthDB GarthDB force-pushed the main branch 2 times, most recently from ee6236e to 0127f82 Compare July 16, 2025 19:50
@GarthDB GarthDB closed this Aug 4, 2025
@GarthDB GarthDB deleted the snyk-upgrade-0b93562a5f824bdb46ba1795d6493a97 branch September 19, 2025 20:28
GarthDB added a commit that referenced this pull request Jan 22, 2026
Root cause: changesets/action is designed for NPM_TOKEN authentication
and doesn't fully support npm's OIDC trusted publishing (issue #515).
When using the built-in 'publish' parameter, changesets/action tries
to manage npm authentication, which blocks npm 11.6.2's OIDC auto-detection.

Solution: Use changesets/action's 'custom publishing' approach:
- changesets/action only handles versioning and PR creation
- Separate step runs 'pnpm release' when hasChangesets == 'false'
- npm 11.6.2 handles OIDC authentication automatically

This is the recommended approach from the changesets/action README
for custom authentication setups.

References:
- https://github.com/changesets/action#custom-publishing
- changesets/action#515

Changes:
- Removed 'publish: pnpm release' from changesets/action
- Added custom 'Publish to npm with OIDC' step
- Triggers only when there are no new changesets (time to publish)
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.

3 participants