Skip to content
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

feat: Rename aes128Key to aesKey to allow aes256 in the future #5990

Merged
merged 1 commit into from
Dec 5, 2023

Conversation

avelad
Copy link
Member

@avelad avelad commented Dec 5, 2023

@avelad avelad added type: enhancement New feature or request priority: P4 Nice to have / wishful thinking labels Dec 5, 2023
@avelad avelad added this to the v5.0 milestone Dec 5, 2023
@avelad avelad changed the title feat: Rename aes128Key by aesKey to allow aes256 in the future feat: Rename aes128Key to aesKey to allow aes256 in the future Dec 5, 2023
@avelad avelad requested a review from theodab December 5, 2023 09:58
@shaka-bot
Copy link
Collaborator

shaka-bot commented Dec 5, 2023

Incremental code coverage: 92.21%

@avelad avelad merged commit 31c06ca into shaka-project:main Dec 5, 2023
14 of 15 checks passed
@avelad avelad deleted the aes-key branch January 8, 2024 08:36
@shaka-bot shaka-bot added the status: archived Archived and locked; will not be updated label Feb 3, 2024
@shaka-project shaka-project locked as resolved and limited conversation to collaborators Feb 3, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
priority: P4 Nice to have / wishful thinking status: archived Archived and locked; will not be updated type: enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants