1 days ago
lego

v5.5.2

lego is an independent, free, and open-source project, if you value it, consider supporting it! ❤️

Everybody thinks that the others will donate, but in the end, nobody does.

So if you think that lego is worth it, please consider donating.

For key updates, see the changelog.

Changelog

2 days ago
wails

Wails v3.0.0-beta.25

Wails v3 Beta Release - v3.0.0-beta.25

Fixed

  • Stop wails3 dev and its background processes when the primary application exits (#6048)

🤖 This is an automated nightly release generated from the latest changes on master.

Installation:

go install github.com/wailsapp/wails/v3/cmd/wails3@v3.0.0-beta.25

⚠️ Beta Warning: This is pre-release software. The API is stable, but you may still encounter issues before the final 3.0 release.

2 days ago
sarama

Version 1.61.0 (2026-09-22)

What's Changed

🎉 New Features / Improvements

🐛 Fixes

📦 Dependency updates

🔧 Maintenance

📝 Documentation

New Contributors

Full Changelog: https://github.com/IBM/sarama/compare/v1.60.2...v1.61.0

3 days ago
unioffice

v2.14.0

Release notes - UniOffice v2.14.0

This release contains new features, improvements and bug fixes.

New Features

  • US-1698 Image compression API for DOCX: Document.CompressImages(targetDPI, jpegQuality), the equivalent of Word's "Compress Pictures"
  • US-1749 XLOOKUP, XMATCH, SWITCH and TEXTSPLIT for the spreadsheet formula engine
  • US-1750 Statistical functions for the spreadsheet formula engine: the STDEV/VAR family, NORM.DIST, NORM.INV, BINOM.DIST, PERCENTILE, QUARTILE, CORREL, FORECAST and LINEST
  • US-1783 Presentation text formatting and slide property API: italic, underline, strike, caps, character spacing, kerning, superscript/subscript, language, line spacing, margins, indents and tab stops, plus Slide.SetHidden/Hidden, SlideSize.SetType/Type and Presentation.NotesSize/SetNotesSize

Improvements

  • US-1658 XLSX to PDF conversion honoring print areas, including multi-range lists, whole-column and whole-row references
  • US-1665 DOCX to PDF rendering of Word section formatting: multi-column layout, page borders, line numbering and page-number formats
  • US-1761 UniPDF dependency update to v5.1.0
  • US-1699 CI/CD pipeline gating convert render output against committed baselines, with stale-baseline detection and pixel-diff artifacts on failure

Bug Fixes

  • US-1729 Table of contents not generated for content wrapped in a Structured Document Tag (SDT) fix
  • US-1749 INDEX panicking out of bounds when the column argument equals the row width fix
  • US-1658 XLSX to PDF fixes for the page size table (missing Quarto and Envelope 9 codes, swapped Envelope B5 dimensions, incorrect Monarch width), charts duplicating series data from both live and cached values, mis-sized merged cells, and page-break artifacts in row borders and trailing pages

Breaking Changes

  • US-1761 The minimum supported Go version is now 1.25.0, raised by the UniPDF v5.1.0 dependency. Projects building UniOffice with Go 1.24 or earlier need to upgrade their toolchain.
3 days ago
go-micro

v6.14.0

What's Changed

New Contributors

Full Changelog: https://github.com/micro/go-micro/compare/v6.13.0...v6.14.0

3 days ago
sessions

v1.1.2

Changelog

Others

  • 30faf8469f7727b2b78dd4409745bb62991753da: chore(deps)!: fix Trivy security findings (#313) (@appleboy)
4 days ago
validator

Release 10.30.5

What's Changed

New Contributors

Full Changelog: https://github.com/go-playground/validator/compare/v10.30.4...v10.30.5

4 days ago
wails

Wails v3.0.0-beta.24

Wails v3 Beta Release - v3.0.0-beta.24

Security

  • Restrict GITHUB_TOKEN permissions in build and publish workflows to follow the principle of least privilege
  • Fix path traversal and symlink escapes in the screen example asset middleware
  • Keep setup wizard dependency installation functional while restricting it to approved package-manager commands

🤖 This is an automated nightly release generated from the latest changes on master.

Installation:

go install github.com/wailsapp/wails/v3/cmd/wails3@v3.0.0-beta.24

⚠️ Beta Warning: This is pre-release software. The API is stable, but you may still encounter issues before the final 3.0 release.

4 days ago
pdfcpu

v0.16.0-rc.1

pdfcpu v0.16.0-rc.1

This release candidate is available for testing.

Please try it with your existing workflows and report regressions before the final v0.16.0 release.

Highlights

  • Updated Go API — Explicit contexts for long-running operations, optional progress reporting, and reusable caller-owned configuration.
  • Configuration redesign — Schema-aware loading, explicit initialization and reset, plus read-only and stateless operation.
  • Automation and container preparation — Signal cancellation, safer output replacement, password-file inputs, and verified execution under arbitrary user IDs.
  • Stronger PDF validation — Improved malformed-input handling, graph-traversal safeguards, and compatibility warnings for selected relaxed-validation decisions.
  • Clearer signature validation — Separate reporting of document integrity, certificate trust, revocation, and timestamp evidence.
  • PDF processing fixes — Improved resize orientation, rotated watermarks, form appearances, image handling, and LZW decoding.
  • Smaller Go module — Approximately 94% smaller in the original packaging comparison. Samples and test fixtures remain in Git but are excluded from module downloads.

Requirements and installation

Go applications require Go 1.26 or later and updates to affected API calls. Existing file-backed configurations from v0.15 or earlier require an explicit configuration reset.

go get github.com/pdfcpu/pdfcpu@v0.16.0-rc.1

Before upgrading

Reset legacy file-backed configuration

Existing v0.15 and older config.yml files do not contain the new configuration schema identifier. pdfcpu preserves the file and reports that a reset is required instead of rewriting it automatically.

If the configuration is not customized, run:

pdfcpu config reset
pdfcpu config validate

For an explicit configuration root, use the same root for every command:

pdfcpu --conf /srv/pdfcpu config reset
pdfcpu --conf /srv/pdfcpu config validate
pdfcpu --conf /srv/pdfcpu config inspect

Installed user fonts and trusted certificates are preserved.

Before resetting, back up any customized config.yml.
After resetting, reapply your settings. Installed fonts and trusted certificates are preserved.
New installations and stateless operation with --conf disable need no migration.

See the v0.16 configuration upgrade guide.

Update Go API callers

Change Required action
Long-running operations require a context.Context Pass the request or job context, or context.Background() when cancellation is not needed. Nil contexts are rejected.
Validation and optimization operations take a final *api.ProgressOptions Pass nil when progress events are not needed.
LoadConfiguration() now takes options and returns an error Call api.LoadConfiguration(api.ConfigurationOptions{}) and handle the error.
Context-free and interim WithContext/WithOptions variants were consolidated Use the canonical operation name.

Configurations supplied by an application remain caller-owned and can be reused after an operation. Clone a configuration before applying different settings for another job; do not mutate it concurrently while operations use it. Passing nil loads the default configuration and may initialize files on disk. For stateless applications, explicitly load api.ConfigurationModeStateless and pass the returned configuration.

See API installation and usage and the v0.16 migration guide for before/after examples.

Configuration and runtime

Explicit configuration modes

  • Automatic discovers or initializes file-backed configuration for normal CLI and API use.
  • Read-only loads a prepared configuration tree without modifying it.
  • Stateless uses built-in settings and the 14 core PDF fonts without accessing configuration files, user fonts or the local certificate store.

The CLI selects stateless mode with --conf disable.
Applications select a mode through api.ConfigurationOptions.
Configuration root precedence is the explicit flag, PDFCPU_CONFIG_ROOT, then the operating-system default.
Normal CLI PDF commands have no read-only-mode flag: prepare the complete tree first and mount it read-only.
Go applications can select api.ConfigurationModeReadOnly to load existing configuration without modifying files.

The new commands are:

pdfcpu config init
pdfcpu config list
pdfcpu config inspect [--json]
pdfcpu config validate
pdfcpu config reset

Use pdfcpu config inspect for configuration paths and effective policy.

Cancellation and transactional output

The CLI responds to Ctrl+C, SIGINT and SIGTERM. The first signal requests a clean stop; a second signal terminates immediately. Go callers control cancellation through the context passed to the operation.

Cancellation is cooperative, so a large operation may take a moment to reach a safe stopping point. File-producing operations stage output before publication. When cancellation or an ordinary write failure occurs before publication, an existing destination is preserved and unfinished temporary output is removed.

Stdin PDF input and merged form multi-fill output to stdout use the operating-system temporary directory. Replacement files are staged beside their destination. On supported Unix systems, replacement preserves the destination group or fails before publication.

Password files

Use --upw-file or --opw-file wherever the corresponding literal password flag is accepted. Supply a password either directly or through a file, not both. Password files cannot use stdin.

One trailing LF or CRLF is ignored. Other spaces and line endings remain part of the password. An empty file supplies an empty password, except where a non-empty owner password is required.

Password changes can replace their positional old/new password pair with:

Command Old password New password
changeupw --upwold-file --upwnew-file
changeopw --opwold-file --opwnew-file

Both file options for a password change must be supplied together.

Resource and network policy

  • maxInputBytes optionally limits each PDF input, including stdin spooling. Zero remains unlimited.
  • maxObjectBytes exposes the existing per-object reader buffer limit. Its default remains 64 MiB.
  • Offline mode now consistently covers remote images, link validation and live CRL/OCSP requests.
  • Outbound image and revocation requests reject loopback, private, link-local, multicast, unspecified and selected special-purpose destinations by default. Trusted private revocation hosts can be configured explicitly.

These settings limit individual inputs or operations; they are not a total memory, disk or job-time budget.

Validation

Compatibility warnings

Compatibility-warning coverage has substantially expanded. Relaxed validation reports selected conditions that strict validation would reject, indicating whether content was accepted, skipped or repaired in memory. These warnings are available through the CLI and structured API reports; --quiet suppresses CLI warnings.

Go callers can obtain the same ordered report through ValidateWithReport, ValidateFileWithReport and ValidateContextWithReport. Existing error-only validation APIs remain available.

The v0.16.0 coverage is intentionally bounded and will be extended gradually.
Right now it covers the parser vertical slice and selected Type 1 font, remote destination, annotation, Type 3 function, simple-font width and Indexed-image mask compatibility paths changed for this release. Other existing relaxed parser, reader and validator fallbacks may not produce a structured notice. The absence of a notice does not prove that relaxed validation followed the strict path.

Strict validation describes the checks pdfcpu currently implements; it does not certify complete ISO 32000 compliance or prove that no bounded low-level reader recovery occurred.

Expanded validation and malformed-input handling

Stronger validation and safer handling of malformed PDFs, including improved bounds checks, cycle detection and error reporting. Relaxed mode adds targeted compatibility exceptions while strict validation retains its requirements.

Signature-validation evidence

Signature validation now separates established evidence from the overall local assessment. Compact output includes an Integrity: line. Full output groups cryptographic signature, signed-content digest, profile, signer certificate, certificate path, revocation and timestamp evidence before presenting the assessment.

unknown means that evidence was unavailable, inconclusive or not checked; it does not mean success.

Document timestamps receive the supported local RFC 3161 CMS-signature, message-imprint, profile, TSA-certificate and configured-local path checks. Embedded signature timestamp tokens are located and parsed, including their generation time, but are not yet authenticated. Timestamp presence alone does not establish PAdES B-T.

pdfcpu reports local technical evidence.
It does not make enterprise-policy, legal-validity, eIDAS, qualified-signature or complete long-term-validation decisions.
PAdES classification remains limited to the supported B-B result.

See signature validation for the complete output and current limitations.

Distribution and constrained environments

The Go module now excludes samples and test fixtures while retaining all runtime resources (#1449).
This release prepares pdfcpu for container deployment; an official image is planned for v0.17.

Compatibility summary

  • Existing v0.15 and older file-backed configuration requires an explicit reset.
  • Long-running Go APIs require a non-nil context under their canonical names.
  • Validation and optimization APIs listed above require the final progress argument.
  • Strict validation may reject malformed structures that earlier releases did not check.
  • Relaxed compatibility warnings do not yet cover every pre-existing fallback.
  • Cancellation takes effect at checkpoints, so some operations may not stop immediately.

Fixed issues

#1407, #1444, #1449, #1457, #1460, #1461, #1465, #1466, #1467, #1470, #1472, #1473, #1474, #1477, #1479, #1484, #1485, #1487.