Repository navigation
Bump fast-uri from 3.1.8 to 3.1.9 in /frontend - #515
Merged
fabiodalez-dev merged 10 commits intoNov 5, 2026
Merged
Conversation
…fcwm ubuntu-latest now resolves to 26.04, where Playwright cannot install Chromium, so every browser job fails before running a test. I pin the runners to 24.04 until Playwright supports the new image. npm audit blocks on GHSA-mf2p-h6hf-fcwm (tinymce 8.5.1-8.9.2, media plugin serialization XSS). The lockfile moves to 8.10.0; the editor served from public/assets/tinymce is unchanged.
The tinymce bump only reached node_modules, while the app loads the committed copy in public/assets/tinymce, which was still 8.1.2. That copy is now refreshed from the locked 8.10.0 package (same file set: the dom model, silver theme, oxide and tinymce-5 skins, default icons and the existing plugins; license.md added, CHANGELOG.md stays ignored). copy-vendor-assets.js now copies TinyMCE as well, so the existing "git diff --exit-code -- public/assets" gates in the release and supply chain workflows fail whenever a tinymce bump is not followed by the refreshed files.
The "Scan complete Git history with Gitleaks" step passes on pull_request and push events, which only scan the changed range, but fails on every scheduled and manual run: the full-history scan reports 28 findings in commits from 2025, all documentation placeholders (api-book-scraper guide and README, the curl example on the advanced settings tab), array literals and French translation strings matched by the generic rule, and the RFC 8291 Appendix A web-push test vectors. None is a credential. Record their fingerprints in .gitleaksignore so the weekly scan on main is green again and a real leak would be visible.
npm ci runs the postinstall copy, which put node_modules/tinymce/CHANGELOG.md (gitignored, 300 KB) into public/assets/tinymce, and build-release.sh rsyncs the working tree, so the release ZIP carried a file that is not in the repository. The copy now skips it and .rsync-filter excludes it as a second guard. The log line names the real destination.
Bumps [fast-uri](https://github.com/fastify/fast-uri) from 3.1.8 to 3.1.9. - [Release notes](https://github.com/fastify/fast-uri/releases) - [Commits](fastify/fast-uri@v3.1.8...v3.1.9) --- updated-dependencies: - dependency-name: fast-uri dependency-version: 3.1.9 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
|
Important Review skippedBot user detected. To trigger a single review, invoke the
 |
Owner
Code reviewBranch: Found 1 finding across all lanes: Deep lane — correctness & securityNo confirmed findings. One candidate was checked and disproven: |
dependabot
Bot
deleted the
dependabot/npm_and_yarn/frontend/fast-uri-3.1.9
branch
November 5, 2026 21:51
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.
Bumps fast-uri from 3.1.8 to 3.1.9.
Release notes
Sourced from fast-uri's releases.
Commits
0def703Bumped v3.1.9a1d0da2test: generate only relative path references9eb8759fix: preserve relative paths in suffix and relative resolution54c30f7docs: note suffix-reference authority ambiguity39e6493fix: escape a first-segment colon in suffix references745183ctest: cover first-segment colon in suffix referencesddfc6a5fix(SEC-03): reject non reg-name characters in domain hostsd86a8d2fix: keep a colon-first segment behind "./" in relative normalizationeb483b5test: cover colon-first relative references in normalizationb110a35fix(SEC-02): preserve meaning of relative references during normalizationMaintainer changes
This version was pushed to npm by GitHub Actions, a new releaser for fast-uri since your current version.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.
Review update — 2026-11-04
Current main and the shared mobile-test login prerequisite from #503 are incorporated. The dependency change remains exactly fast-uri 3.1.8 → 3.1.9 (version, resolved URL and integrity); the only additional source change is the three-line consent handling in the browser test helper.
Local installation and ESLint pass. The production build passes with the repository's required Node 22 runtime, and generated assets remain unchanged. This branch's complete history is integrated in #521; all three PR heads must have green checks before the release integration merges.