Skip to content

base64ct: update changelog entry for v1.7.0 with yanked tag #1694

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Mar 5, 2025

Conversation

newpavlov
Copy link
Member

No description provided.

@tarcieri
Copy link
Member

tarcieri commented Mar 5, 2025

We can potentially consider un-yanking it, FWIW

@newpavlov
Copy link
Member Author

newpavlov commented Mar 5, 2025

I am fine with either. Releasing v2 would result in less complaints and a bit leaner dep specs (base64ct="2" vs base64ct="1.7").

@newpavlov
Copy link
Member Author

Opened #1695 to discuss what to do with v1.7.0.

@newpavlov
Copy link
Member Author

I will merge it for now. It can be reverted later in the case of v1.7.0 un-yanking.

@newpavlov newpavlov merged commit d5bee49 into master Mar 5, 2025
53 checks passed
@newpavlov newpavlov deleted the base64ct/yanked branch March 5, 2025 14:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants