fix: update repository URLs from czottmann/linearis to linearis-oss/linearis#72
Merged
Conversation
…inearis npm publish with --provenance fails with E404 because the OIDC token from linearis-oss/linearis does not match the czottmann/linearis repository URL in package.json. Update repository, bugs, and homepage URLs in package.json and all documentation referencing the old repository.
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.
Problem
npm publish --provenancefails withE404because the OIDC token issued by GitHub Actions forlinearis-oss/linearisdoes not match theczottmann/linearisrepository URL inpackage.json. npm's provenance verification rejects the mismatch.See: https://github.com/linearis-oss/linearis/actions/runs/24093992364/job/70287901207
Fix
Update all repository references from
czottmann/linearistolinearis-oss/linearis:package.json:repository.url,bugs.url,homepageCHANGELOG.md: v2026.4.1 compare/issue linksdocs/deployment.md: clone and install URLsCONTRIBUTING.md: clone URL.github/ISSUE_TEMPLATE/config.yml: security policy linkHistorical CHANGELOG entries (≤ v2025.12.3) intentionally keep the old URLs since those PRs/issues live on the original repo.
After merge
Re-tag and push to re-trigger the publish:
git tag -d v2026.4.1 git push origin :refs/tags/v2026.4.1 git tag -a v2026.4.1 -m "Release 2026.4.1" git push origin v2026.4.1