v4.2.1: Misredirect Request

This release doesn't have any code-fundemental changes, all dependencies are updated. uwu <3

Full Changelog: 4.2.0...4.2.1

v4.2.0: Blaze It! :fire:

weed number lmao

Additions

• ume screenshot now supports Ume 3.x
• [gridfs] repl_set_name is now supported under the env configuration

Fixes

• Defers color-eyre's installation as it fail under ume screenshot:

~ » ume screenshot default
Error: cannot install provided ErrorHook, a hook has already been installed

Location:
     /tmp/nix-build-ume-4.1.0.drv-0/ume-4.1.0-vendor/color-eyre-0.6.3/src/config.rs:704:9

• When parsing a Sentry DSN, it'll panic! if the dsn is invalid. Now, it'll report a error and abort the process.
• When providing a server URL and no uploader key to ume screenshot, the error message now conveys the right way:

# 4.1.0:
$ ume screenshot http://localhost
May 02, 2025 - 18:27:53 PM WARN  Tried to initialize the wayland data control protocol clipboard, but failed. Falling back to the X11 clipboard protocol. The error was: Unknown error while interacting with the clipboard: A required Wayland protocol (zwlr_data_control_manager_v1 version 1) is not supported by the compositor
May 02, 2025 - 18:27:53 PM INFO  loading CLI configuration... path=/home/noel/.config/Noel/ume/config.toml
Error:
   0: expected `--uploader-key` to be present if `<SERVER>` argument is a valid URI

Location:
   src/cli/cmds/screenshot.rs:272

# 4.2.0:
May 02, 2025 - 18:29:16 PM WARN  unknown  Tried to initialize the wayland data control protocol clipboard, but failed. Falling back to the X11 clipboard protocol. The error was: Unknown error while interacting with the clipboard: A required Wayland protocol (ext-data-control, or wlr-data-control version 1) is not supported by the compositor
May 02, 2025 - 18:29:16 PM INFO  ume::cli::config  loading CLI configuration... path=/home/noel/.config/Noel/ume/config.toml
Error: 
   0: expected `<UPLOADER KEY>` argument to be present if `<SERVER>` argument is a valid URI

• Better Wayland detection for flameshot usage
  • before it would error out like this (view console log below)
  • now it'll work as expected

May 02, 2025 - 18:23:36 PM WARN  Tried to initialize the wayland data control protocol clipboard, but failed. Falling back to the X11 clipboard protocol. The error was: Unknown error while interacting with the clipboard: A required Wayland protocol (zwlr_data_control_manager_v1 version 1) is not supported by the compositor
May 02, 2025 - 18:23:36 PM INFO  loading CLI configuration... path=/home/noel/.config/Noel/ume/config.toml
May 02, 2025 - 18:23:36 PM INFO  $ /run/current-system/sw/bin/flameshot gui -r
Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway.
flameshot: error: Unable to capture screen
flameshot: error: Unable to capture screen
QLayout: Attempting to add QLayout "" to SidePanelWidget "", which already has a layout
flameshot: info: Screenshot aborted.
May 02, 2025 - 18:23:36 PM ERROR failed to run screenshot

Full Changelog: 4.1.0...4.2.0

v4.1.0: Gone

This release removes all the deprecations that were mentioned in v4.0.6

• The ume CLI now provides a configuration interface over configuring uploaders for ume screenshot. It is in the TOML format of:

# enables system notifications, use `false` to disable it.
system_notifications = true

[[uploader]]
url = "http://localhost:3621"
key = "<your uploader key>"
name = "my-uploader"

All uploaders can be referenced by their name, i.e, ume screenshot my-uploader.

• GNOME Screenshot is now supported. You can use --gnome-screenshot or the GNOME_SCREENSHOT environment to enable it or provide a path to a gnome-screenshot binary.
• The ume binary should be less in the actual size of the binary.

Full Changelog: 4.0.6...4.1.0

v4.0.6: Not Acceptable

This release is just a dependency update release, functionality hasn't been changed (or has broke yet).

Deprecations

• HCL-based configuration format is deprecated and will be removed in v4.1.0 (@auguwu)
• tracing.opentelemetry.kind is deprecated and will detect via the URL (tracing.opentelemetry.url) scheme (@auguwu)

Full Changelog: 4.0.5...4.0.6

v4.0.5: Method Not Allowed

• Updated Azalia libraries, logging should look different now~!
• The clipboard when ume screenshot is used will be initialized first, if no clipboard can be used then the URL for the image will not be copied, it'll be printed to the standard output.
• When using the ume package in a Nix flake/configuration.nix, shell completions are installed.

Full Changelog: 4.0.4...4.0.5

v4.0.4: Not Found

🐛 Fixes

• ARM64 builds for ume should be included (@auguwu)

✨ Dependency Updates

Kind	Name	From	To	By
GitHub Action	taiki-e/cache-cargo-install-action	v1	v2	@renovate-bot in #201
Rust crate	mimalloc	v0.1.39	v0.1.41	@renovate-bot in #198
Rust crate	aws-sdk-s3	v1.23.0	v1.31.0	@renovate-bot in #199, #209, #215, #218, #219, #221, #235, #237
Rust crate	serde	v1.0.198	v1.0.203	@renovate-bot in #202, #208, #216, #222, #244
Rust crate	remi	v0.7.0	v0.8.0	@renovate-bot in #203, @auguwu in commit b8716419
Rust crate	remi-fs	v0.7.0	v0.8.0	@renovate-bot in #205, @auguwu in commit b8716419
Rust crate	remi-s3	v0.7.0	v0.8.0	@renovate-bot in #207, @auguwu in commit b8716419
Rust crate	remi-gridfs	v0.7.0	v0.8.0	@renovate-bot in #206, @auguwu in commit b8716419
Rust crate	remi-azure	v0.7.0	v0.8.0	@auguwu in commit b8716419

• Update rust Docker tag to v1.78 by @renovate-bot in #210
• Update Rust crate multer to 3.1.0 by @renovate-bot in #211
• Update Rust crate tokio-util to 0.7.11 by @renovate-bot in #212
• Update Rust crate syn to v2.0.61 by @renovate-bot in #214
• Update Rust crate serde_json to v1.0.117 by @renovate-bot in #217
• Update Rust crate syn to v2.0.63 by @renovate-bot in #220
• Update cachix/install-nix-action action to v27 by @renovate-bot in #226
• Update Rust crate syn to v2.0.64 by @renovate-bot in #227
• Update Rust crate hcl-rs to 0.17.0 by @renovate-bot in #228
• Update Rust crate syn to v2.0.65 by @renovate-bot in #229
• Update Rust crate hcl-rs to v0.17.1 by @renovate-bot in #230
• Update Rust crate mimalloc to v0.1.42 by @renovate-bot in #231
• Update cachix/cachix-action action to v15 by @renovate-bot in #232
• Update Rust crate hcl-rs to v0.17.2 by @renovate-bot in #233
• Update alpine Docker tag to v3.20 by @renovate-bot in #234
• Update Rust crate syn to v2.0.66 by @renovate-bot in #236
• Update Rust crate hcl-rs to 0.18.0 by @renovate-bot in #243
• Update sentry-rust monorepo to 0.33.0 by @renovate-bot in #245

Full Changelog: 4.0.3...4.0.4

v4.0.3: Forbidden

➕ Additions

• Added configuring the data storage driver with system environment variables if UME_STORAGE_SERVICE was 'gridfs' (@auguwu)

Full Changelog: 4.0.2...4.0.3

v4.0.2

🐛 Fixes

• Do not panic when UME_STORAGE_S3_ENFORCE_PATH_ACCESS_STYLE or UME_STORAGE_S3_ENABLE_SIGNER_V4_REQUESTS don't exist or include invalid UTF-8
• Do not panic when UME_STORAGE_AZURE_EMULATOR_PORT doesn't exist or includes invalid UTF-8

v4.0.1

➕ Additions

• Added basic OpenTelemetry support, which will report all tracing::Spans. This only supports OpenTelemetry collector.
• Added support for copying all uploaded images with the ume screenshot that is supported on Windows, macOS, and Linux. You can disable this from the --no-copy or UME_NO_COPY=1 environment variable

🐛 Fixes

• Fixed from erroring when ume screenshot cannot upload to a Ume server for some reason.
• Fix regression when parsing UME_TRACING_OTEL_LABELS. in v4.0.0, it'll just loop indefinitely, in v4.0.1, it'll skip invalid strings and parse key=value.
• Fixed issues when no uploader_key was specified. It should generate and use that random one instead of an empty string.

v4.0.0

this is literally my 19th try and im sorry if i keep spamming, i hate ci so much

This is the v4 release of ume that supports the local filesystem, Amazon S3, and Azure Blob Storage so you don't need to rely on MongoDB GridFS!

Migration

Migration is easy as updating the environment variables:

• AUTH to UME_UPLOADER_KEY

and updating DB and DB_URL in ume.hcl:

storage "gridfs" {
  database = "<whatever $DB was>"
  bucket = "<bucket name to use, defaults to the db name>"
  client_options {
    hosts = ["<whatever $DB_URL was>"]
  }
}

Full Changelog: 3.3.0...4.0.0