Skip to content

chore: version packages - #53

Merged
bendersej merged 1 commit into
mainfrom
changeset-release/main
Sep 28, 2026
Merged

bendersej merged 1 commit into
mainfrom
changeset-release/main

Conversation

@github-actions

@github-actions github-actions Bot commented Sep 28, 2026 •

Copy link
Copy Markdown
Contributor

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@simplepdf/web-embed-pdf@1.9.0

Minor Changes

  • 3afba3b: Your pages are now ready for AI agents. While the editor is open, an agent in your visitor's browser (ChatGPT's browser, Chrome with WebMCP) can read and fill the form, move between pages and submit it, with the same permissions as any other integration. It is on by default: add webmcp="false" to the script tag to turn it off.
    • More PDF links open in SimplePDF: Report.PDF, form.pdf?v=2 and guide.pdf#page=3 used to open in the browser.
    • Japanese and Dutch: pages in either language open the editor in that language.
    • Stored documents open directly: a link to a SimplePDF document (/documents/<id>) opens it in the editor.
    • Clear errors for invalid company identifiers: a value that cannot form an editor address (a URL, spaces, dots, underscores) logs an error and opens nothing. An identifier without an account still opens the editor, which explains the problem.
    • Same script, same API: now built on @simplepdf/embed, the engine behind the React component. window.simplePDF, the script-tag attributes and the modal are unchanged.

bendersej added a commit that referenced this pull request Sep 28, 2026
…ed changelog (#54)

## Background

The version PR #53 failed **Web / Formatting**: the 1.9.0 changeset has
a blank line between its lead paragraph and its list, which `changeset
version` turns into a blank line inside a list item that Prettier
rejects. The failure only showed in the version PR, after the feature PR
had merged. The version PR should only ever contain generated output,
never a formatting fix.

## Changes

- The root `version` script is a pure `changeset version` (no
formatter), for every package.
- New **Changelog Check** workflow on pull requests touching a package,
a changeset or the root `package.json`: it runs the release's `npm run
version`, then the formatting checks the version PR runs, so a changeset
whose generated CHANGELOG is not formatted fails the pull request that
adds it.
- The pending 1.9.0 changeset: the blank line before its list is
removed.

## Notes

- Verified locally with the pure `version` script: the original 1.9.0
changeset fails the check (as #53 did) and the fixed one passes.
- Once merged, the release workflow rebuilds #53 from the fixed
changeset, with nothing to reformat.
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 77e3242 to 8f42e76 Compare September 28, 2026 09:26
@bendersej
bendersej merged commit 44ad492 into main Sep 28, 2026
3 checks passed
@bendersej
bendersej deleted the changeset-release/main branch September 28, 2026 09:31
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