This repository has been archived by the owner on May 5, 2024. It is now read-only.
Deprecation of aws-ssm-secrets and keybase-notifications packages #661
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR addresses the deprecation of the
aws-ssm-secrets
andkeybase-notifications
packages.The following changes have been made:
aws-ssm-secrets
andkeybase-notifications
packages to prevent automatic updates..eslintignore
and.prettierignore
files to exclude the deprecated actions.README.md
files to reflect the deprecation and provide information on alternative solutions.Disclaimer:
In addition to the deprecation of packages, I have also made updates to dev dependencies. I have done this in a single pull request because it was difficult for me to find the time to split it into fractional updates, considering the need to learn the deprecated interfaces of outdated packages. I hope you understand the reason behind this unfortunate action.
List of additional changes made:
Out of Scope:
I want to clarify that I have not addressed any logic related to the release process in this pull request. As per our agreement, the responsibility for handling the release process lies with Santiago Bernhardt @sbe-arg . Therefore, any changes or updates specific to the release process are not included in this PR.
Please review the changes and merge this PR to complete the deprecation process for these actions.