chore(ci): switch npm publish to Trusted Publishing (OIDC)#1
Merged
Conversation
Drops NPM_TOKEN in favour of npm's OIDC-based Trusted Publishing. The workflow's id-token permission lets npm verify it was invoked by this exact workflow on this exact repo, and provenance is attached to the published tarball. Requires a one-time setup on npmjs.com: package settings → Publishing access → Add trusted publisher with org=QualityUnit, repo=harnext, workflow=release.yml. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
yasha-dev1
added a commit
that referenced
this pull request
Jun 16, 2026
) A large or multi-line paste was inserted inline into the single-line textarea buffer (newlines flattened to spaces), which exploded the input across many wrapped rows and mangled the frame/caret math — and lost the original newlines. Now a paste above a threshold (any newline, or > 200 chars) is kept in a per-textarea paste store and represented by a compact placeholder token (`[Pasted text #1 +12 lines]`), expanded back to the exact original text (newlines preserved) at submit. Small single-line pastes inline as before. - paste-store.ts (new, pure/unit-tested): shouldStorePaste threshold, register → placeholder, expand (multiple tokens; unknown look-alikes left as typed), tokenEndingAt for atomic deletion, clear (ids stay monotonic). - input.ts: Ctrl+V stores large pastes; backspace at a token's right edge deletes the whole token (and frees its entry); submit expands placeholders and clears the store. Scope: the Ctrl+V/onPaste path (deterministic). Capturing raw terminal bracketed paste (the path behind the IntelliJ-terminal hang, #60) needs stdin-level work and is a follow-up. Tests: 14 unit (paste-store) + 4 textarea integration (multiline round-trip with newlines preserved, embedded placeholder, single-backspace atomic delete, short paste still inlined); updated the prior newline-flatten test to the new preserve-newlines behavior. Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
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
NPM_TOKENfrom the release workflow in favour of npm's OIDC-based Trusted Publishing — no long-lived secret to rotate or leak.--provenance --access publicso published tarballs get a verifiable build attestation linking them to this workflow run.@latestin the runner because Node 20 ships npm 10 and OIDC publish needs npm >= 11.5.Required before this can publish
harnextpackage → Settings → Publishing access → Add trusted publisher:QualityUnitharnextrelease.ymlNPM_TOKENrepo secret.Test plan
dry_run = true— exercises the OIDC handshake without uploading.vX.Y.Zto do a real publish; verify the published version on npm shows the provenance badge.🤖 Generated with Claude Code