Repository navigation
chore: release @monetizationos/proxy - #47
Merged
Merged
Conversation
There was a problem hiding this comment.
🟡 Changes recommended
The required removeAndKeepContent() method breaks existing consumer adapters at type-checking or runtime, so releasing it as 1.9.0 needs either a major version bump or an optional method with a fallback.
1 open issue
What changed in this PR
Prepares @monetizationos/proxy 1.9.0 for automated publication, recording the range-replacement optimization introduced in #43.
Changes:
- Bumps the package version and request-header version to 1.9.0.
- Adds release notes covering range-replacement performance, buffering behavior, and the new adapter requirement.
- Removes the consumed changeset.
| File | Description |
|---|---|
src/apiRequestHeaders.ts |
Updates the reported proxy version to 1.9.0. |
package.json |
Sets the release version to 1.9.0. |
CHANGELOG.md |
Adds the 1.9.0 release notes. |
.changeset/range-wrapper-cut.md |
Removes the changeset incorporated into the changelog. |
Review effort: Balanced
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
November 6, 2026 15:43
25e45bf to
62fa04c
Compare
benney
self-requested a review
November 6, 2026 16:29
benney
approved these changes
Nov 6, 2026
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
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.

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
@monetizationos/proxy@1.9.0
Minor Changes
#43
f440059Thanks @benney! - Range replacement cuts the range with one callback instead of one per element when the start and end markers are direct children of the container. Other pages are cut element by element as before.RewriterElementnow requiresremoveAndKeepContent, which lol-html andHTMLRewriterelements already implement. A page with a range is now buffered before it is rewritten, and HTML comments inside the cut range are removed with it.#45
74e9663Thanks @benney! - More pages use the one-callback range cut. Content other components insert inside the range is removed with it, whatever the component order, and a marker removed by another component still marks where the range starts or ends. A container holding raw text, such astextareaorscript, is left alone, and only the outermost of nested containers is cut. Selector lists, several range components in one decision, and other content on the range component all use the one-callback path. Selector lists also apply per part when cutting element by element. A start marker nested inside its container now uses the one-callback path too, when its range is the only one in the decision.