Repository navigation
chore: update module github.com/greenpau/caddy-security to v1.7.0 - autoclosed - #1999
Closed
renovate[bot] wants to merge 1 commit into
Closed
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
Contributor
|
You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool. What Enabling Code Scanning Means:
For more information about GitHub Code Scanning, check out the documentation. |
Contributor
✅ Supply Chain Verification Results✅ PASSED 📦 SBOM Summary
🔍 Vulnerability Scan
📎 Artifacts
Generated by Supply Chain Verification workflow • View Details |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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:
1.6.2→1.7.0Release Notes
greenpau/caddy-security (github.com/greenpau/caddy-security)
v1.7.0Compare Source
Caddy Security v1.7.0 upgrades go-authcrunch from v1.5.0 to v1.6.0 and brings identity-bound profile, password-management, and encrypted Documents workflows to the optional SQLite identity backend.
sqlite, regardless of its realm name. AuthCrunch implementation, Caddy integration.GET <portal-mount>/api/capabilitiesreports backend identity, supported operations, configuration state, permissions, and signing-key availability. Clients can distinguish unavailable features from disabled or forbidden ones. Discovery does not replace each API's authorization checks. Upstream change.storage_unavailablefromcommit_uncertain. Upstream implementation.//or/\, escapes inferred mount segments once, and scopes legacy signing-failure diagnostics to the individual event. Runtime change, route-contract regressions.crewjam/samlto v0.6.3 andgolang.org/x/netto v0.62.0 through AuthCrunch v1.6.0, including signed-response regression coverage for SAML subject namespaces. Upgradeklauspost/compressto v1.20.2 for GO-2026-6865. CI and release builds use Go 1.26.11. AuthCrunch dependency fixes, Caddy dependency updates.For upgrades, SQLite companions remain opt-in build modules; the standard Caddy release binary does not automatically include them. Existing Profile, Admin, and Documents configuration controls apply, with no new Caddyfile switch for this integration. The existing SQLite account schema, account UUIDs, enrollment tombstones, and encrypted document format are preserved. Stop/start preserves accounts and vault ownership but requires fresh login evidence; already issued stateless access tokens retain their bounded lifetime.
API clients should handle structured SQLite administration fields and treat missing credential counts as unsupported rather than zero. Administrative mutations retain their HTTP-200 failure envelopes, so inspect the response body. Account and Documents writes are separate transactions: reconcile a
commit_uncertainresult before retrying a mutation. Within this SQLite identity store, API keys, public-key collections, MFA, stored login rules, connected accounts, and downstream OIDC provider realms remain unsupported. Full capability-aware UI integration remains separate work.The verified SAML namespace correction does not remove the unbounded affected-version range in GO-2026-6909; scanners may still report that advisory. Legacy OpenPGP findings match the module, but the affected deprecated packages are absent from the qualified production binaries. Residual SAML and historical Caddy advisory assessments are retained rather than suppressed. This release does not claim that every scanner finding is resolved.
Release validation and publication passed for the exact v1.7.0 tag, and the CodeQL workflow completed successfully. Pre-release qualification included race-enabled Go unit/E2E tests with Chrome and Consul, SQLite handoff and Documents journeys, all twelve cross-built command targets, and 36 packaged configuration checks. Official OIDC conformance was not part of this qualification. Release workflow, CodeQL workflow.
Release assets include Caddy and
caddy-authenticatorarchives for Linux, macOS, and Windows on amd64 and arm64, plusauthcrunch_1.7.0_SHA256SUMS.The upstream range also adds web-app and React authentication guidance and a Documents test-driver-only CodeQL exception. These are contributor tooling changes, not additional runtime capabilities or a Caddy-wide scanner exception.
Full comparisons: Caddy Security v1.6.2 → v1.7.0, go-authcrunch v1.5.0 → v1.6.0.
Configuration
📅 Schedule: (in timezone America/New_York)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.