Skip to content

Release 0.3.1: the repository moved to github.com/fynepdf - #14

Merged
birazzzz merged 2 commits into
mainfrom
release/v0.3.1
Oct 31, 2026
Merged

birazzzz merged 2 commits into
mainfrom
release/v0.3.1

Conversation

@birazzzz

Copy link
Copy Markdown
Collaborator

The repository moved from birazzzz to the fynepdf organisation. GitHub redirects the old links.

  • Version 0.3.1. Nothing changes in how wrapguard works.
  • Every link says github.com/fynepdf/wrapguard: package.json repository/homepage/bugs, the README (CI badge, demo image, uses: fynepdf/wrapguard@v0, issues) and the PR comment's credit line.
  • RELEASING.md: what a move means for npm's trusted publisher. npm can't edit one, so a new one goes in for fynepdf/wrapguard, and it has to be used by a publish within 2 days.

npm needs repository.url to match the repository that publishes, so this has to be on main before the v0.3.1 release.

- Version 0.3.1. Nothing changes in how wrapguard works.
- Every link says github.com/fynepdf/wrapguard: package.json repository/homepage/bugs, the README
  (CI badge, demo image, `uses: fynepdf/wrapguard@v0`, issues) and the PR comment's credit line.
  GitHub redirects the old birazzzz links.
- RELEASING.md: what a move means for npm's trusted publisher.
ubuntu-latest became Ubuntu 26.04, where the locked Playwright 1.56 has no Chromium, so the test
job and the release's tests failed at "Install Chromium". The action's self-test stays on
ubuntu-latest: it installs the newest Playwright, as users get.
@birazzzz
birazzzz merged commit 3c04caf into main Oct 31, 2026
3 checks passed
birazzzz added a commit that referenced this pull request Nov 1, 2026
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.

1 participant