Skip to content

fix: Switch not_valid_after to not_valid_after_utc#144

Merged
piraz merged 1 commit intodevelopfrom
switch_to_lsnot_valid_after_utc
Aug 30, 2025
Merged

fix: Switch not_valid_after to not_valid_after_utc#144
piraz merged 1 commit intodevelopfrom
switch_to_lsnot_valid_after_utc

Conversation

@piraz
Copy link

@piraz piraz commented Aug 30, 2025

Co-authored-by: GitHub Copilot <131524155+github-copilot[bot]@users.noreply.github.com>

Refs: #137

Co-authored-by: GitHub Copilot <131524155+github-copilot[bot]@users.noreply.github.com>

Refs: #137
@piraz piraz added this to the 0.9.15 milestone Aug 30, 2025
@piraz piraz self-assigned this Aug 30, 2025
@piraz piraz added the bug Something isn't working label Aug 30, 2025
@piraz piraz merged commit 5344ddb into develop Aug 30, 2025
10 of 11 checks passed
@piraz piraz deleted the switch_to_lsnot_valid_after_utc branch August 30, 2025 03:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants