chore: bump @matters/matters-editor to 0.3.3 - #6002
Merged
Merged
Conversation
The npm publish for 0.3.2/0.3.3 had been failing since PR thematters/matters-editor#525 merged, due to a stale NPM_AUTH_TOKEN secret (last rotated 2020-06-19). The token was rotated and the Publish workflow rerun successfully; npm dist-tag latest is now 0.3.3.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
@matters/matters-editorfrom^0.3.1to^0.3.3(package.json+package-lock.json, no source changes)NPM_AUTH_TOKENGitHub secret on that repo was stale (last rotated 2020-06-19, causing 404s on publish)npm view @matters/matters-editor versionconfirmslatestis now0.3.3Test plan
npm install @matters/matters-editor@0.3.3— lockfile resolves to0.3.3, diff scoped to the two dependency files onlynpm run lint:ts/next lint— not run to a clean result in this environment: fails on pre-existingCannot find module '~/gql/graphql'because the generated GraphQL types requirenpm run gen:typeagainst a live schema, unrelated to this bump. Please confirm CI's codegen step passes lint clean.@matters/matters-editorconsumers) in CI/preview deploy🤖 Generated with Claude Code