Skip to content

Changesets: Versioning & Publication - #87

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
changeset-release/main
Open

Changesets: Versioning & Publication#87
github-actions[bot] wants to merge 1 commit into
mainfrom
changeset-release/main

Conversation

@github-actions

@github-actions github-actions Bot commented Aug 20, 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

@imgproxy/imgproxy-js-core@1.9.0

Minor Changes

  • 020080d: Add support for bypass_cache and cache_tags options (imgproxy Pro). When bypass_cache is set to 1, t or true, imgproxy bypasses the internal cache and does all the processing and fetching from the source image. cache_tags accepts a list of strings that imgproxy adds to the cache entry and the response headers. Both options are supported in processing and image info URLs. The short forms bc and ct are also supported.
  • 4f9ad1b: Make the Gravity union exclusive: fields belonging to one gravity variant are now typed as forbidden (?: never) on the others, so mixing fields from different variants (such as { type: "sm", x_offset: 0 } or { type: "no", x: 0.5 }) is a compile-time error for TypeScript users instead of only a runtime one. Runtime behavior is unchanged. TypeScript code that previously compiled while passing such invalid combinations will now fail to compile — the same combinations have always thrown at runtime.
  • 183d037: Add support for progressive_blur option (imgproxy Pro). When sigma is greater than 0, imgproxy applies a progressive Gaussian blur filter that transitions from no blur at the start position to the specified sigma at the stop position. The option accepts sigma, an optional direction (down, up, right, left, or an angle in degrees), and optional start and stop floats between 0 and 1. The short form pbl is also supported.
  • 043d0b3: Add support for video_thumbnail_keyframes option (imgproxy Pro). When set to 1, t or true, imgproxy uses the latest keyframe before the requested second for video thumbnail generation, redefining the IMGPROXY_VIDEO_THUMBNAIL_KEYFRAMES config. The option is supported in processing and image info URLs. The short form vtk is also supported.

Patch Changes

  • 4f9ad1b: Fix optional arguments being checked for truthiness instead of presence in resize, size, watermark, watermark_size, trim, unsharp_masking, png_options, jpeg_options, colorize, monochrome and gravity. Falsy but invalid values (such as null or an empty color) skipped validation and were silently rendered as omitted arguments, so { watermark_size: { width: null, height: 100 } } produced wms::100 instead of raising. Such values now raise an error, and explicitly provided 0 values are rendered instead of being dropped. colorize.color and monochrome.color are now validated as hex colors, matching trim.color and gradient.color.

    Also fix jpeg_options rejecting progressive: false when optimize_scans was set to false. The cross-check now applies only when optimize_scans is actually enabled.

  • c124469: Fix video_thumbnail_animation generating URLs containing the literal string undefined when frame_width or frame_height was omitted. Both arguments are required by imgproxy and by the option's type, so they are now validated like step, delay and frames, and a missing value raises an error instead of producing a broken URL.

    Fix zoom silently ignoring a zoom value of 0. The option was dropped before validation, so no error was raised. imgproxy requires zoom factors to be greater than 0, so 0 is now rejected for zoom, zoom_x and zoom_y. Note that this changes the error message for non-positive values from "can't be less than 0" to "can't be less or equal than 0".

  • a97d0ef: Fix the gradient option dropping optional arguments explicitly set to 0. color, direction, start and stop were checked for truthiness, so { gradient: { opacity: 0.5, stop: 0 } } produced gr:0.5 and imgproxy fell back to the default stop of 1.0 instead of the requested 0. The same applied to start: 0 and to a direction angle of 0. These values are now rendered explicitly, and invalid falsy values (such as null or an empty color) are reported instead of being silently ignored.

@github-actions
github-actions Bot force-pushed the changeset-release/main branch 4 times, most recently from 78dbbf6 to 82ac27b Compare August 21, 2026 07:47
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 82ac27b to ae8db6e Compare August 24, 2026 12:50
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