BREAKING CHANGE(SmartAcme): Refactor challenge handling by removing legacy setChallenge/removeChallenge in favor of pluggable challengeHandlers and update documentation and tests accordingly
This commit is contained in:
@@ -1,5 +1,13 @@
|
||||
# Changelog
|
||||
|
||||
## 2025-04-27 - 6.0.0 - BREAKING CHANGE(SmartAcme)
|
||||
Refactor challenge handling by removing legacy setChallenge/removeChallenge in favor of pluggable challengeHandlers and update documentation and tests accordingly
|
||||
|
||||
- Removed legacy challenge methods and introduced new 'challengeHandlers' and 'challengePriority' options
|
||||
- Updated readme examples to demonstrate usage with DNS-01 (and HTTP-01) handlers
|
||||
- Refactored internal SmartAcme flow to select and process challenges via the new handler interface
|
||||
- Adjusted tests (including integration tests) to align with the updated challenge handling mechanism
|
||||
|
||||
## 2025-04-27 - 5.1.0 - feat(smartacme)
|
||||
Implement exponential backoff retry logic and graceful shutdown handling in SmartAcme; update acme-client dependency to v5.4.0
|
||||
|
||||
|
||||
Reference in New Issue
Block a user