Andreas/watchtower
1
0
Fork 0
mirror of https://github.com/containrrr/watchtower.git synced 2025-12-16 15:10:12 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions
watchtower/docs/SUMMARY_CHECKPOINT.md
kalvinparker e1f67fc3d0 feat(registry): add support for custom CA certificates and TLS validation 
- Introduced `--registry-ca` and `--registry-ca-validate` flags for configuring TLS verification with private registries.
- Implemented in-memory token caching with expiration handling.
- Updated documentation to reflect new CLI options and usage examples.
- Added tests for token cache concurrency and expiry behavior.
2025-11-14 14:30:37 +00:00

1.5 KiB
Raw Blame History

Summary Checkpoint

This file marks a checkpoint for summarizing repository changes.

All future requests that ask to "summarise all the changes thus far" should consider only changes made after this checkpoint was created.

Checkpoint timestamp (UTC): 2025-11-13T12:00:00Z

Notes:

  • Purpose: act as a stable anchor so that subsequent "summarise all the changes thus far" requests will include only modifications after this point.
  • Location: docs/SUMMARY_CHECKPOINT.md

Recent delta (since previous checkpoint):

  • Added CLI flags and wiring: --registry-ca and --registry-ca-validate (startup validation).
  • Implemented secure-by-default registry transport behavior and support for a custom CA bundle.
  • Introduced an in-memory bearer token cache (honors expires_in) and refactored time usage to allow deterministic tests via an injectable now function.
  • Added deterministic unit tests for the token cache (pkg/registry/auth/auth_cache_test.go).
  • Added quickstart documentation snippets to README.md, docs/index.md, and docs/private-registries.md showing --registry-ca + --registry-ca-validate.
  • Created CHANGELOG.md with an Unreleased entry for the new --registry-ca-validate flag.
  • Ran package tests locally: pkg/registry/auth and pkg/registry/digest — tests passed (some integration tests were skipped due to missing credentials).

If you want the next checkpoint after more changes (e.g., mapping the update call chain, documenting data shapes, or adding concurrency tests), request another summary break.