Skip to content

fix(deps): update all non-major dependencies - #3

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/all-minor-patch
Open

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/all-minor-patch

Conversation

@renovate

@renovate renovate Bot commented Jan 19, 2026

Copy link
Copy Markdown

This PR contains the following updates:

Package Change Age Confidence
@types/node (source) 20.19.3020.19.43 age confidence
eslint-plugin-react-refresh ^0.4.14^0.5.0 age confidence
github.com/klippa-app/go-pdfium v1.17.2v1.20.3 age confidence
typescript (source) ~5.6.3~5.9.0 age confidence

Release Notes

ArnaudBarre/eslint-plugin-react-refresh (eslint-plugin-react-refresh)

v0.5.7

Compare Source

Add allowCompoundComponents option (#​117)

Default: false (true in vite config)

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-react 4.7.0, @vitejs/plugin-react-swc 3.11.0.

{
  "react-refresh/only-export-components": [
    "error",
    { "allowCompoundComponents": true }
  ]
}

Enabling this option allows code such as the following:

const Root = () => <></>;
const Label = () => <></>;
export const Tag = { Root, Label };

v0.5.6

Compare Source

  • Support re-exporting namespace components (fixes #​116)

v0.5.5

Compare Source

  • Fix SCREAMING_SNAKE_CASE constant exported via export { Name } incorrectly treated as React component #​114 (fixes #​113)
  • Add contentType and size to allowExportNames in Next config #​115

v0.5.4

Compare Source

  • Add instant to allowExportNames in Next config #​112

v0.5.3

Compare Source

  • Fix check for non component class exported via export { } #​110 (fixes #​109)

v0.5.2

Compare Source

  • Support nested function calls for extraHOCs (actually fixes #​104)

v0.5.1

Compare Source

  • Mark ESLint v10 as supported
  • Support false positives with TypeScript function overloading (fixes #​105)
  • Support nested function calls for extraHOCs (fixes #​104)

v0.5.0

Compare Source

Breaking changes
  • The package now ships as ESM and requires ESLint 9 + node 20. Because legacy config doesn't support ESM, this requires to use flat config
  • A new reactRefresh export is available and prefered over the default export. It's an object with two properties:
    • plugin: The plugin object with the rules
    • configs: 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.
  • customHOCs option was renamed to extraHOCs
  • Validation of HOCs calls is now more strict, you may need to add some HOCs to the extraHOCs option

Config example:

import { defineConfig } from "eslint/config";
import { reactRefresh } from "eslint-plugin-react-refresh";

export default defineConfig(
  /* Main config */
  reactRefresh.configs.vite({ extraHOCs: ["someLibHOC"] }),
);

Config example without config:

import { defineConfig } from "eslint/config";
import { reactRefresh } from "eslint-plugin-react-refresh";

export default defineConfig({
  files: ["**/*.ts", "**/*.tsx"],
  plugins: {
    // other plugins
    "react-refresh": reactRefresh.plugin,
  },
  rules: {
    // other rules
    "react-refresh/only-export-components": [
      "warn",
      { extraHOCs: ["someLibHOC"] },
    ],
  },
});
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 like export 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"] }
  ]
}

[!NOTE]
Actually createRoute functions from TanStack Router are not React HOCs, they return route objects that fake to be a memoized component but are not. When only doing createRootRoute({ component: Foo }), HMR will work fine, but as soon as you add a prop to the options that is not a React component, HMR will not work. I would recommend to avoid adding any TanStack function to extraHOCs it you want to preserve good HMR in the long term. Bluesky thread.

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 connect from the rule. If you are using connect from react-redux, you should now add it to extraHOCs like this:

{
  "react-refresh/only-export-components": ["warn", { "extraHOCs": ["connect"] }]
}
klippa-app/go-pdfium (github.com/klippa-app/go-pdfium)

v1.20.3

Compare 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.2

Compare 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)

GetPageTextStructured with CollectFontInformation used FPDFText_GetCharIndexAtPos at 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. FontInformation is still never nil.

FPDFPage_Flatten reloads 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, render ByIndex" happened to work.

After a flatten that returns Success, both backends reload the page behind the given reference. ByReference and ByIndex callers 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 on FPDFPage_Flatten).

FPDF_RenderPage accepts real Windows device context handles (#​370, supersedes #​270)

The Windows-only FPDF_RenderPage required request.DC to be a C.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.Handle or unsafe.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.1

Compare Source

What's Changed

Full Changelog: klippa-app/go-pdfium@v1.20.0...v1.20.1

Functional changes

  • WASM: JPEG encoding no longer duplicates the bitmap in guest memory (PR #​364, levmv). Rendered bitmaps already live in WASM memory, so the encoder now borrows the bitmap's guest offset instead of allocating a second full-size buffer and copying the pixels in. The Go-owned fallback copy path is kept for images composited in Go. Peak guest memory for a JPEG render drops by roughly one bitmap.
  • WASM: render internals refactored around a renderedPages type (PR #​364, #​366). The four render methods now share internal helpers that return the pixel offset and cleanup function together. RenderToFile was 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.
  • Both runtimes: transparent pages are flattened onto white in place (PR #​365). The old code allocated a second RGBA image and used image/draw. The new renderutil.CompositeOnWhiteInPlace blends straight-alpha pixels into the existing buffer with integer arithmetic that is bit-identical to the draw.Over result, 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.
  • Minor allocation tweak: the 16-byte JPEG output-parameter block is now allocated with MallocNoZero since the shim always writes it.

Tests

  • New internal/renderutil/composite_test.go verifies the in-place blend against image/draw, and checks stride padding, opaque pixels and fully transparent pixels.
  • New internal/implementation_webassembly/jpeg_memory_test.go renders 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.
  • The WASM implementation suite gained a shared memory-limited pool and a WAZERO_INTERPRETER=1 switch so the interpreter CI job really runs every spec interpreted.
  • The bitmap-allocation error test moved from the public webassembly package 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 by any in 133 places, including the public Pdfium.GetImplementation return type and the FPDFBitmap_CreateEx.Pointer and FPDF_RenderPage.DC request fields. Source-compatible.
  • Deprecated io/ioutil removed: ReadFile, WriteFile, TempFile, ReadAll and ReadDir now use their os and io equivalents. Over 220 call sites, nearly all in shared_tests.
  • Legacy // +build lines dropped from 37 files that already had //go:build.
  • Counted loops rewritten as for i := range n, reflect.TypeOf((*T)(nil)).Elem() replaced by reflect.TypeFor[T](), and the text-extractor bucket clamp now uses built-in min and max.

v1.20.0

Compare 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:

  • WebAssembly: the runtime now caches the module methods
  • WebAssembly: some methods now don't zero-out the claimed memory because all memory would be overwritten anyway
  • WebAssembly: malloc now uses memset to clear out the claimed memory instead of writing all nil bytes from Go
  • WebAssembly: Wazero now uses the faster exception handling methods
  • WebAssembly: JPEG rendering now happens through the turbo-jpeg vendored by PDFium directly in WebAssembly, its not as fast as in CGO but still a lot faster than native Golang JPEG
  • Webassembly: build with build flags -flto and -O3 for optimal performance
  • Structured text extraction is now much faster because we now do our own rect comparison, it matches the output of PDFium but is just much faster because it has to do way less calls into PDFium

PDFium instructions (upstreamed, released, please update to PDFium 8044 to benefit from them):

  • PNG decoding improvements (CL 155510)
  • Composite opaque BGR rows improvements (CL 155530)
  • CStretchEngine improvements (155550)

PDFium instructions (upstreamed, not released yet, WebAssembly build only for now):

  • JPEG decode improvements (CL 156070 + 156090, merged)
  • Unicode charcode mapping fix (CL 156290, merged)
  • Image decode improvements (CL 155971, not merged yet)
  • CStretchEngine improvements for alpha arm (CL 156110)

PDFium WebAssembly performance patches:

  • Allow using memset for filling memory
  • Implement WASM SIMD for CStretchEngine
  • Implement WASM SIMD for ScanLineCompositor
  • Implement WASM SIMD in zlib
  • Implement WASM SIMD in libjpeg-turbo

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
Operation v1.19.8 v1.20.0 Aggregate change
Structured text 1.92 ms/page 1.15 ms/page −40.2%
Render (150 DPI) 6.75 ms/page 5.03 ms/page −25.4%
WebAssembly - go-pdfium v1.19.8 vs v1.20.0 - PDFium 7961 vs 8044
Operation v1.19.8 v1.20.0 Aggregate change
Structured text 6.33 ms/page 2.02 ms/page −68.2%
Render (150 DPI) 20.37 ms/page 11.61 ms/page −43.0%
RenderToFile JPEG end-to-end 29.99 ms/page 15.98 ms/page −46.7%
Implied JPEG encode 8.49 ms/page 3.18 ms/page −62.5%

PDFium update to 8044

PDFium has been updated to 8044 and the new experimental methods FPDFBookmark_GetStyle, FPDFPath_GetBezierControlPoints, FORM_GetTextDirection, and FORM_SetTextDirection. The WebAssembly version is now compiled with Emscripten 6.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.

  • The form fill timer did not use proper locking, which could use unintended deadlocks
  • Data availability handlers were not properly tracked and could also be destroyed while still in use
  • Bitmap external buffers were not properly tracked for GC
  • Passing user fonts in InitLibrary did not end the array with a nil item, which could cause issues when the claimed memory was not zero'ed
  • If a bitmap could not be created the whole rendering fails properly now

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.8

Compare Source

What's Changed

Full Changelog: klippa-app/go-pdfium@v1.19.7...v1.19.8

v1.19.7

Compare Source

What's Changed

  • Fix flaky document open error reporting on Windows by @​jerbob92 in #​337
    • When you open a document in Pdfium, you first do the open call and then do another call to check what the error code was, in the Windows implementation of Pdfium, the error collection is bound to the OS thread, it may happen that different CGO calls happen over different OS threads, which sometimes caused Pdfium to not report the error correctly that happened in the document open call. This change forces both CGO calls to happen on the same thread, so that the error reporting of opening a document always works correctly on Windows.
  • fix: resolve build failure on 32-bit architectures (386/arm) due to oversized Cgo array type- #​335 by @​maa3x in #​336

New Contributors

Full Changelog: klippa-app/go-pdfium@v1.19.6...v1.19.7

v1.19.6

Compare Source

What's Changed

  • webassembly: allow omitting embedded WASM from linked binaries by @​levmv in #​334

Full Changelog: klippa-app/go-pdfium@v1.19.5...v1.19.6

v1.19.5

Compare Source

What's Changed

  • Bump github.com/onsi/ginkgo/v2 from 2.29.0 to 2.32.0 by @​dependabot[bot] in #​325
  • Bump google.golang.org/grpc from 1.79.3 to 1.82.1 by @​dependabot[bot] in #​330
  • Bump golang.org/x/text from 0.38.0 to 0.40.0 by @​dependabot[bot] in #​328
  • webassembly: allow caller-provided context by @​levmv in #​331
  • Read file data directly into WebAssembly memory by @​levmv in #​332
  • Bump github.com/onsi/gomega from 1.41.0 to 1.42.1 by @​dependabot[bot] in #​326
  • Bump golang.org/x/net from 0.56.0 to 0.57.0 by @​dependabot[bot] in #​329
  • Update to pdfium 7961 by @​jerbob92 in #​333
    • Update Pdfium to 7961 (including WebAssembly build with Emscripten version 6.0.0)
    • Implement new experimental pdfium methods:
      • FPDFAttachment_GetDescription
      • FPDFAttachment_SetDescription
      • FPDFBookmark_GetColor

New Contributors

Full Changelog: klippa-app/go-pdfium@v1.19.4...v1.19.5

v1.19.4

Compare Source

What's Changed

  • Bump golang.org/x/net from 0.53.0 to 0.54.0 by @​dependabot[bot] in #​314
  • Bump github.com/onsi/ginkgo/v2 from 2.28.3 to 2.29.0 by @​dependabot[bot] in #​315
  • Bump github.com/onsi/gomega from 1.40.0 to 1.41.0 by @​dependabot[bot] in #​316
  • Bump golang.org/x/text from 0.37.0 to 0.38.0 by @​dependabot[bot] in #​319
  • Bump github.com/tetratelabs/wazero from 1.11.0 to 1.12.0 by @​dependabot[bot] in #​318
  • Bump golang.org/x/net from 0.54.0 to 0.55.0 by @​dependabot[bot] in #​317
  • Update pdfium to 7881 by @​jerbob92 in #​320
    • Update Pdfium to 7881 (including WebAssembly build with new Emscripten version 6.0.0)
    • Implement new experimental pdfium methods:
      • FPDFPageObj_AddExistingMark
      • FPDFText_SetPositions
      • FPDFTextObj_SetFontSize

Full Changelog: klippa-app/go-pdfium@v1.19.3...v1.19.4

v1.19.3

Compare Source

What's Changed

New Contributors

Full Changelog: klippa-app/go-pdfium@v1.19.2...v1.19.3

v1.19.2

Compare Source

What's Changed

  • Wazero interpreter fix and tests by @​jerbob92 in #​307
    • This fixes a very specific bug that would only appear on the Webassembly runtime, using the interpreter runtime, and with very specific experimental methods related to fonts (FPDFText_LoadCidType2Font, FPDFFont_GetGlyphWidth, FPDFFont_GetGlyphPath, FPDFGlyphPath_GetGlyphPathSegment)

Full Changelog: klippa-app/go-pdfium@v1.19.1...v1.19.2

v1.19.1

Compare Source

What's Changed

  • Upgrade to pdfium 7789 by @​jerbob92 in #​306
    • Update WebAssembly version to 7789 (with Emscripten update to 5.0.5)

Full Changelog: klippa-app/go-pdfium@v1.19.0...v1.19.1

v1.19.0

Compare Source

What's Changed

  • Update pdfium to 7776 by @​jerbob92 in #​304
    • Update WebAssembly version to 7776
    • Implemented new experimental methods FPDFCatalog_GetLanguage, FPDFPageObjMark_GetParamFloatValue, FPDFPageObjMark_SetFloatParam, FPDF_StructElement_GetExpansion,
    • Fixed experimental method 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.1

Compare Source

What's Changed

New Contributors

Full Changelog: klippa-app/go-pdfium@v1.18.0...v1.18.1

v1.18.0

Compare Source

What's Changed

Full Changelog: klippa-app/go-pdfium@v1.17.3...v1.18.0

v1.17.3

Compare 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.3

Compare 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.9

Compare 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.3

Compare 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.8

Compare Source

For release notes, check out the release announcement.

Downloads are available on:

v5.7.3: TypeScript 5.7.3

Compare Source

For release notes, check out the release announcement.

Downloads are available on npm

v5.7.2: TypeScript 5.7

Compare Source

For release notes, check out the release announcement.

Downloads are available on:


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • Between 12:00 AM and 03:59 AM, only on Monday (* 0-3 * * 1)
  • Automerge
    • At any time (no schedule defined)

🚦 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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
renovate Bot requested a review from NickTitle as a code owner January 19, 2026 00:28
@renovate
renovate Bot force-pushed the renovate/all-minor-patch branch from 27c79d2 to bf48eb1 Compare January 20, 2026 16:02
@renovate renovate Bot changed the title chore(deps): update dependency typescript to ~5.9.0 Update dependency typescript to ~5.9.0 Jan 20, 2026
@renovate
renovate Bot force-pushed the renovate/all-minor-patch branch from bf48eb1 to fd9c54c Compare February 2, 2026 06:57
@renovate renovate Bot changed the title Update dependency typescript to ~5.9.0 Update all non-major dependencies Feb 2, 2026
@renovate
renovate Bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 59bcec3 to 3cd47a5 Compare February 8, 2026 03:22
@renovate
renovate Bot force-pushed the renovate/all-minor-patch branch from 3cd47a5 to 5d6ad4f Compare February 13, 2026 07:49
@renovate

renovate Bot commented Feb 13, 2026

Copy link
Copy Markdown
Author

ℹ️ Artifact update notice

File name: backend/go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

  • 3 additional dependencies were updated
  • The go directive was updated for compatibility reasons

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 minimumReleaseAge=48 hours

Details:

Package Change
go 1.25.3 -> 1.26.0
github.com/tetratelabs/wazero v1.9.0 -> v1.12.0
golang.org/x/net v0.44.0 -> v0.59.0
golang.org/x/text v0.29.0 -> v0.42.0

@renovate
renovate Bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from ba46dba to d87d061 Compare March 1, 2026 12:00
@renovate
renovate Bot force-pushed the renovate/all-minor-patch branch from d87d061 to 2007713 Compare March 8, 2026 09:45
@renovate renovate Bot changed the title Update all non-major dependencies fix(deps): update all non-major dependencies Mar 24, 2026
@renovate
renovate Bot force-pushed the renovate/all-minor-patch branch from 2007713 to 2de5e1a Compare April 1, 2026 16:32
@renovate
renovate Bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 080b5ff to f7e4aab Compare April 19, 2026 04:14
@renovate
renovate Bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 0e10bda to 01ea177 Compare May 14, 2026 11:28
@renovate
renovate Bot force-pushed the renovate/all-minor-patch branch from 01ea177 to b7f0af2 Compare June 13, 2026 03:51
@renovate
renovate Bot force-pushed the renovate/all-minor-patch branch from b7f0af2 to 31c6c6b Compare June 20, 2026 23:44
@renovate
renovate Bot force-pushed the renovate/all-minor-patch branch from 31c6c6b to b1e8d99 Compare July 30, 2026 00:16
@renovate
renovate Bot force-pushed the renovate/all-minor-patch branch from b1e8d99 to fdd6832 Compare August 15, 2026 04:11
@renovate
renovate Bot force-pushed the renovate/all-minor-patch branch from fdd6832 to 3550119 Compare August 29, 2026 07:47
@renovate
renovate Bot force-pushed the renovate/all-minor-patch branch from 3550119 to 559038e Compare September 6, 2026 03:14
@renovate
renovate Bot force-pushed the renovate/all-minor-patch branch from 559038e to bd3a069 Compare September 19, 2026 19:52
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.

0 participants