mirror of
https://codeberg.org/forgejo/forgejo.git
synced 2024-11-10 01:05:14 +00:00
2 commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
Earl Warren
|
1171069ced
|
docs(release-notes): flatten release-notes files
It is not for the developer to keep them sorted in a hierarchy when the release they belong to can be deduced from the tag of the release into which they were merged. The release notes assistant does that work instead. Some files appeared in more than one directory (feat and fix for instance) when the PR contains multiple unrelated commits which is what happens on a regular basis with the weekly cherry-pick of Gitea. Those files were merged into one and each line changed to start with a conventional commit prefix (feat: fix:). Each line in a file will be a separate line in the release notes, they are not groupped together even when they relate to the same PR. The determination of the category in which they should be displayed will be based on regular expressions using either the PR title or the line to add to the release notes itself. Unify the content of each file to either be a bullet list of independent pull requests or be folded into a single line if it is multiline. Multiline content belongs to the documentation. Refs: https://code.forgejo.org/forgejo/release-notes-assistant Refs: https://www.conventionalcommits.org/en/v1.0.0/ |
||
|
Renovate Bot
|
8672ad12b1 |
Update module github.com/caddyserver/certmagic to v0.21.0 (#3724)
This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [github.com/caddyserver/certmagic](https://github.com/caddyserver/certmagic) | require | minor | `v0.20.0` -> `v0.21.0` | --- ### Release Notes <details> <summary>caddyserver/certmagic (github.com/caddyserver/certmagic)</summary> ### [`v0.21.0`](https://github.com/caddyserver/certmagic/releases/tag/v0.21.0) [Compare Source](https://github.com/caddyserver/certmagic/compare/v0.20.0...v0.21.0) CertMagic v0.21 introduces some big changes: - Draft support for draft-03 of [ACME Renewal Information (ARI)](https://datatracker.ietf.org/doc/draft-ietf-acme-ari/) which assists with deciding when to renew certificates. This augments CertMagic's already-advanced logic using cert lifetime and OCSP/revocation status. - New [`ZeroSSLIssuer`](https://pkg.go.dev/github.com/caddyserver/certmagic@v0.21.0#ZeroSSLIssuer) uses the [ZeroSSL API](https://zerossl.com/documentation/api/) to get certificates. ZeroSSL also has an ACME endpoint, which can still be accesed using the existing ACMEIssuer, as always. Their proprietary API is paid, but has extra features like IP certificates, better reliability, and support. - DNS challenges should be smoother in some cases as we've improved propagation checking. - In the odd case your ACME account disappears from the ACME server, CertMagic will automatically retry with a new account. (This happens in some test/dev environments.) - ACME accounts are identified only by their public keys, but CertMagic maps accounts by CA+email for practical/storage reasons. So now you can "pin" an account key to use by specifying your email and the account public key in your config, which is useful if you need to absolutely be sure to use a specific account (like if you get rate limit exemptions from a CA). Please try it out and report any issues! Thanks to [@​Framer](https://github.com/Framer) for their contributions to this release! #### What's Changed - Bump golang.org/x/crypto from 0.14.0 to 0.17.0 by [@​dependabot](https://github.com/dependabot) in https://github.com/caddyserver/certmagic/pull/264 - Demote "storage cleaning happened too recently" from WARN to INFO by [@​francislavoie](https://github.com/francislavoie) in https://github.com/caddyserver/certmagic/pull/270 - Check DNS propagation at authoritative nameservers only with default resolvers by [@​pgeh](https://github.com/pgeh) in https://github.com/caddyserver/certmagic/pull/274 - Retry with new account if account disappeared remotely by [@​mholt](https://github.com/mholt) in https://github.com/caddyserver/certmagic/pull/269 - Update readme examples to use TLS-ALPN const from ACMEz by [@​goksan](https://github.com/goksan) in https://github.com/caddyserver/certmagic/pull/277 - Initial implementation of ZeroSSL API issuer by [@​mholt](https://github.com/mholt) in https://github.com/caddyserver/certmagic/pull/279 - Allow deleting directories via FileStorage by [@​goksan](https://github.com/goksan) in https://github.com/caddyserver/certmagic/pull/282 - Use the `email` configuration in the ACME issuer to "pin" an account to a key by [@​ankon](https://github.com/ankon) in https://github.com/caddyserver/certmagic/pull/283 - Initial implementation of ARI by [@​mholt](https://github.com/mholt) in https://github.com/caddyserver/certmagic/pull/286 #### New Contributors - [@​pgeh](https://github.com/pgeh) made their first contribution in https://github.com/caddyserver/certmagic/pull/274 - [@​goksan](https://github.com/goksan) made their first contribution in https://github.com/caddyserver/certmagic/pull/277 **Full Changelog**: https://github.com/caddyserver/certmagic/compare/v0.20.0...v0.21.0 </details> --- ### Configuration 📅 **Schedule**: Branch creation - "before 4am" (UTC), Automerge - "before 4am" (UTC). 🚦 **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. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy4zNTEuMiIsInVwZGF0ZWRJblZlciI6IjM3LjM1MS4yIiwidGFyZ2V0QnJhbmNoIjoiZm9yZ2VqbyIsImxhYmVscyI6W119--> Co-authored-by: Earl Warren <contact@earl-warren.org> Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/3724 Reviewed-by: Earl Warren <earl-warren@noreply.codeberg.org> Co-authored-by: Renovate Bot <forgejo-renovate-action@forgejo.org> Co-committed-by: Renovate Bot <forgejo-renovate-action@forgejo.org> |