Seeking Maintainers for Deprecated Actions

[Enase]

We have a few actions in our repository that are now deprecated and no longer actively maintained. We are reaching out to the community to find potential maintainers who are interested in taking over these projects and ensuring their continued development and support.

Deprecated Actions

The following actions are currently marked as deprecated (related PR):

• Keybase Build Notifications
• AWS SSM Build Secrets

How You Can Help

If you are interested in contributing or becoming the new maintainer for any of these actions, we encourage you to get involved. By taking over the maintenance of these projects, you can help ensure their functionality, address any issues, and potentially introduce new features to benefit the wider community.

Next Steps

To express your interest or discuss further details, please comment on this issue.

[sbe-arg]

have build this other action with no intention to replace the complete functionality of this action but link for reference https://github.com/sbe-arg/simple-tags-and-releases

after similar issues with supporting https://github.com/anothrNick/github-tag-action where owners rarely answer any emails and repositories are locked without features necessary in the settings section and maintainers have to do weird un standardized magic to offer a so so solution.

what I have learned so far is that we endup with more bugs on each pr and thats when you get a flow of issues of all the people impacted by them.

these actions tend to be over engineered and attempt to fix all use cases in a single place leading to these problems.

Ill continue to merge prs and review within a few days of creation them but I won't actively do any engineering work on this project.

[crowbarmaster]

I have already started maintaining automatic-releases found here: https://github.com/crowbarmaster/GHactions

I had no original intentions of updating these other two, but after your request, I will re-add them to the project, and get them working with updated depends.

One thing however - without access to the original author's private testing repo, the tests are non-functioning on my own. I will do what I can to recreate these eventually, but I cannot make any guarantees. If someone else would like to re-write the tests to work with a public repo, feel free to open a PR!

Edit: you are a collaborator to this project - does anyone have force push capabilities? I can line this all back up to work with his original testing grounds and submit a PR if so.