fix(deps): update all non-major dependencies - #3
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
from
January 20, 2026 16:02
27c79d2 to
bf48eb1
Compare
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
from
February 2, 2026 06:57
bf48eb1 to
fd9c54c
Compare
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
3 times, most recently
from
February 8, 2026 03:22
59bcec3 to
3cd47a5
Compare
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
from
February 13, 2026 07:49
3cd47a5 to
5d6ad4f
Compare
Author
ℹ️ Artifact update noticeFile name: backend/go.modIn order to perform the update(s) described in the table above, Renovate ran the
Due to Go's usage of Minimal Version Selection (MVS), these packages have been updated to the minimum version available, so will still abide by Details:
|
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
2 times, most recently
from
March 1, 2026 12:00
ba46dba to
d87d061
Compare
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
from
March 8, 2026 09:45
d87d061 to
2007713
Compare
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
from
April 1, 2026 16:32
2007713 to
2de5e1a
Compare
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
2 times, most recently
from
April 19, 2026 04:14
080b5ff to
f7e4aab
Compare
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
3 times, most recently
from
May 14, 2026 11:28
0e10bda to
01ea177
Compare
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
from
June 13, 2026 03:51
01ea177 to
b7f0af2
Compare
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
from
June 20, 2026 23:44
b7f0af2 to
31c6c6b
Compare
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
from
July 30, 2026 00:16
31c6c6b to
b1e8d99
Compare
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
from
August 15, 2026 04:11
b1e8d99 to
fdd6832
Compare
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
from
August 29, 2026 07:47
fdd6832 to
3550119
Compare
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
from
September 6, 2026 03:14
3550119 to
559038e
Compare
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
from
September 19, 2026 19:52
559038e to
bd3a069
Compare
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 contains the following updates:
20.19.30→20.19.43^0.4.14→^0.5.0v1.17.2→v1.20.3~5.6.3→~5.9.0Release Notes
ArnaudBarre/eslint-plugin-react-refresh (eslint-plugin-react-refresh)
v0.5.7Compare Source
Add
allowCompoundComponentsoption (#117)Don't warn when components are exported as an object gathering them. Every member of the object must be a component, and a member holding an anonymous function requires a component name as key.
This should be enabled if the fast refresh implementation correctly handles this case. Vite supports it since
@vitejs/plugin-react4.7.0,@vitejs/plugin-react-swc3.11.0.{ "react-refresh/only-export-components": [ "error", { "allowCompoundComponents": true } ] }Enabling this option allows code such as the following:
v0.5.6Compare Source
v0.5.5Compare Source
export { Name }incorrectly treated as React component #114 (fixes #113)contentTypeandsizetoallowExportNamesin Next config #115v0.5.4Compare Source
instanttoallowExportNamesin Next config #112v0.5.3Compare Source
export { }#110 (fixes #109)v0.5.2Compare Source
v0.5.1Compare Source
v0.5.0Compare Source
Breaking changes
reactRefreshexport is available and prefered over the default export. It's an object with two properties:plugin: The plugin object with the rulesconfigs: An object containing configuration presets, each exposed as a function. These functions accept your custom options, merge them with sensible defaults for that config, and return the final config object.customHOCsoption was renamed toextraHOCsextraHOCsoptionConfig example:
Config example without config:
Why
This version follows a revamp of the internal logic to better make the difference between random call expressions like
export const Enum = Object.keys(Record)and actual React HOC calls likeexport const MemoComponent = memo(Component). (fixes #93)The rule now handles ternaries and patterns like
export default customHOC(props)(Component)which makes it able to correctly support files like this one given this config:{ "react-refresh/only-export-components": [ "warn", { "extraHOCs": ["createRootRouteWithContext"] } ] }Because I'm not 100% sure this new logic doesn't introduce any false positive, this is done in a major-like version. This also give me the occasion to remove the hardcoded
connectfrom the rule. If you are usingconnectfromreact-redux, you should now add it toextraHOCslike this:{ "react-refresh/only-export-components": ["warn", { "extraHOCs": ["connect"] }] }klippa-app/go-pdfium (github.com/klippa-app/go-pdfium)
v1.20.3Compare Source
What's Changed
Full Changelog: klippa-app/go-pdfium@v1.20.2...v1.20.3
PDFium 8057
This release updates the supported PDFium version from 8044 to 8057, for both the CGO and the WebAssembly backend. The bundled WebAssembly module has been rebuilt from 8057.
New API
FPDFPageObj_GetRenderedStrokePattern(experimental): returns a bitmap rasterization of the tiling pattern a page object is stroked with.Performance
Because patches CL 156070 and CL 156090 landed in this release, this gives a nice 6.3% speed improvement when we rendered a testset of 5000 PDFs. This speed improvement is only on the native version, the WebAssembly build already contained the patches since v1.20.0. If you care about rendering performance and use the native build, consider upgrading to PDFium 8057.
v1.20.2Compare Source
What's Changed
Full Changelog: klippa-app/go-pdfium@v1.20.1...v1.20.2
Fixes
Rect font information no longer depends on a tolerance lookup (#368, fixes #23)
GetPageTextStructuredwithCollectFontInformationusedFPDFText_GetCharIndexAtPosat the rect's top-left corner with a hardcoded tolerance of 5 points to find the rect's font. That lookup is wrong by construction: a rect is the union of glyph boxes, so its corner is not on the first char whenever a later char is taller, and the position lookup returns the first char in page order whose box contains the point, from any text object. Measured on the repo corpus, 11% of rects got zero-valued or wrong font information; on a set of 5000 real-world PDFs (1.38M rects), 0.5% did, across 1522 files. No tolerance value fixes it: larger values remove the not-found cases but increase the wrong-font cases.The first char of each rect is now derived from the geometry in
textextract(Extractor.FirstCharIndices), replaying how PDFium builds its rects. Text objects redrawn over each other are disambiguated with the next rect. Verified against an exact ground truth built from text object identity: zero wrong fonts on 1.38M rects.FontInformationis still never nil.FPDFPage_Flattenreloads the page (#369, fixes #199)PDFium parses a page's content when it is loaded and never again. Flattening rewrites the page dictionary, so rendering or extracting text from the same page handle showed the old content with the annotations gone. Only a freshly loaded page showed the flattened result, which is why "flatten
ByReference, renderByIndex" happened to work.After a flatten that returns
Success, both backends reload the page behind the given reference.ByReferenceandByIndexcallers see the flattened content without code changes. Form fill environments that had the page loaded are moved to the reloaded page. The old page stays alive until the handle is closed, so text pages, page objects and annotations obtained before flattening remain valid memory (they keep pointing at the unflattened content, as documented onFPDFPage_Flatten).FPDF_RenderPageaccepts real Windows device context handles (#370, supersedes #270)The Windows-only
FPDF_RenderPagerequiredrequest.DCto be aC.HDC, a cgo type private to the implementation package, so no caller outside it could ever satisfy the type check. It now accepts the handle as the Windows API hands it out:uintptr,syscall.Handleorunsafe.Pointer, with descriptive errors for other types and for a null handle.The dllexport change proposed in #270 is not needed: Go 1.26 removed
__declspec(dllexport)from cgo's generated headers (golang/go#56994), and this module requires Go 1.26. Cross-compiling the cgo backend for Windows with clang was verified to work unmodified.v1.20.1Compare Source
What's Changed
Full Changelog: klippa-app/go-pdfium@v1.20.0...v1.20.1
Functional changes
renderedPagestype (PR #364, #366). The four render methods now share internal helpers that return the pixel offset and cleanup function together.RenderToFilewas rewritten from a four-branch if/else into a switch plus small helpers. The instance lock is now held from render through encode and bitmap release, and is dropped before the encoded image is written to disk so the form-fill timer callback is not starved.image/draw. The newrenderutil.CompositeOnWhiteInPlaceblends straight-alpha pixels into the existing buffer with integer arithmetic that is bit-identical to thedraw.Overresult, so render golden hashes are unchanged. On WASM this also keeps the pixel data inside the guest bitmap so the JPEG borrow above still applies.MallocNoZerosince the shim always writes it.Tests
internal/renderutil/composite_test.goverifies the in-place blend againstimage/draw, and checks stride padding, opaque pixels and fully transparent pixels.internal/implementation_webassembly/jpeg_memory_test.gorenders a synthetic transparent page through all four render paths and both pixel formats under a 48 MiB guest memory cap, and asserts the white compositing result.WAZERO_INTERPRETER=1switch so the interpreter CI job really runs every spec interpreted.webassemblypackage into the internal implementation suite, and the JPEG regression tests were converted to Ginkgo so they count toward coverage.Code modernisation (PR #367, "Code style fixes", mostly mechanical)
interface{}replaced byanyin 133 places, including the publicPdfium.GetImplementationreturn type and theFPDFBitmap_CreateEx.PointerandFPDF_RenderPage.DCrequest fields. Source-compatible.io/ioutilremoved:ReadFile,WriteFile,TempFile,ReadAllandReadDirnow use theirosandioequivalents. Over 220 call sites, nearly all inshared_tests.// +buildlines dropped from 37 files that already had//go:build.for i := range n,reflect.TypeOf((*T)(nil)).Elem()replaced byreflect.TypeFor[T](), and the text-extractor bucket clamp now uses built-inminandmax.v1.20.0Compare Source
What's Changed
New Contributors
Minimum Go version bumped to 1.26
The floor version is now Go 1.26, the CI tests against 1.26 and 1.27.
Performance improvements
A lot of work has been done on improving the performance of go-pdfium and PDFium, especially under WebAssembly.
go-pdfium improvements:
PDFium instructions (upstreamed, released, please update to PDFium 8044 to benefit from them):
PDFium instructions (upstreamed, not released yet, WebAssembly build only for now):
PDFium WebAssembly performance patches:
Exprect more improvements when more is upstreamed. I'm also working on getting SIMD instructions in different parts of PDFium to get even better rendering speeds.
Performance comparisons
CGo - go-pdfium v1.19.8 vs v1.20.0 - PDFium 7961 vs 8044
WebAssembly - go-pdfium v1.19.8 vs v1.20.0 - PDFium 7961 vs 8044
RenderToFileJPEG end-to-endPDFium update to 8044
PDFium has been updated to 8044 and the new experimental methods
FPDFBookmark_GetStyle,FPDFPath_GetBezierControlPoints,FORM_GetTextDirection, andFORM_SetTextDirection. The WebAssembly version is now compiled with Emscripten6.0.9.Race checks and data safety
During the CI, we now check for race conditions which surfaced a few problems that have now been fixed.
PNG compression level support
You can now pick the compression level that you want to use for PNG renders.
Crop support
The render methods now support rendering a part of the page.
Full Changelog: klippa-app/go-pdfium@v1.19.8...v1.20.0
v1.19.8Compare Source
What's Changed
Full Changelog: klippa-app/go-pdfium@v1.19.7...v1.19.8
v1.19.7Compare Source
What's Changed
New Contributors
Full Changelog: klippa-app/go-pdfium@v1.19.6...v1.19.7
v1.19.6Compare Source
What's Changed
Full Changelog: klippa-app/go-pdfium@v1.19.5...v1.19.6
v1.19.5Compare Source
What's Changed
New Contributors
Full Changelog: klippa-app/go-pdfium@v1.19.4...v1.19.5
v1.19.4Compare Source
What's Changed
Full Changelog: klippa-app/go-pdfium@v1.19.3...v1.19.4
v1.19.3Compare Source
What's Changed
New Contributors
Full Changelog: klippa-app/go-pdfium@v1.19.2...v1.19.3
v1.19.2Compare Source
What's Changed
FPDFText_LoadCidType2Font,FPDFFont_GetGlyphWidth,FPDFFont_GetGlyphPath,FPDFGlyphPath_GetGlyphPathSegment)Full Changelog: klippa-app/go-pdfium@v1.19.1...v1.19.2
v1.19.1Compare Source
What's Changed
Full Changelog: klippa-app/go-pdfium@v1.19.0...v1.19.1
v1.19.0Compare Source
What's Changed
FPDFCatalog_GetLanguage,FPDFPageObjMark_GetParamFloatValue,FPDFPageObjMark_SetFloatParam,FPDF_StructElement_GetExpansion,FPDFCatalog_SetLanguage(wrote UTF-8 string in stead of expected UTF-16)Full Changelog: klippa-app/go-pdfium@v1.18.1...v1.19.0
v1.18.1Compare Source
What's Changed
New Contributors
Full Changelog: klippa-app/go-pdfium@v1.18.0...v1.18.1
v1.18.0Compare Source
What's Changed
Full Changelog: klippa-app/go-pdfium@v1.17.3...v1.18.0
v1.17.3Compare Source
What's Changed
Full Changelog: klippa-app/go-pdfium@v1.17.2...v1.17.3
microsoft/TypeScript (typescript)
v5.9.3: TypeScript 5.9.3Compare Source
Note: this tag was recreated to point at the correct commit. The npm package contained the correct content.
For release notes, check out the release announcement
Downloads are available on:
v5.9.2: TypeScript 5.9Compare Source
Note: this tag was recreated to point at the correct commit. The npm package contained the correct content.
For release notes, check out the release announcement
Downloads are available on:
v5.8.3: TypeScript 5.8.3Compare Source
Note: this tag was recreated to point at the correct commit. The npm package contained the correct content.
For release notes, check out the release announcement.
Downloads are available on:
v5.8.2: TypeScript 5.8Compare Source
For release notes, check out the release announcement.
Downloads are available on:
v5.7.3: TypeScript 5.7.3Compare Source
For release notes, check out the release announcement.
Downloads are available on npm
v5.7.2: TypeScript 5.7Compare Source
For release notes, check out the release announcement.
Downloads are available on:
Configuration
📅 Schedule: (UTC)
* 0-3 * * 1)🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.