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

Arguments for switching to self-maintained update workflow #348

Open
Irratzo opened this issue Aug 15, 2024 · 1 comment
Open

Arguments for switching to self-maintained update workflow #348

Irratzo opened this issue Aug 15, 2024 · 1 comment
Labels
configuration Issue refers to the best-of list configuration

Comments

@Irratzo
Copy link
Member

Irratzo commented Aug 15, 2024

Configuration Change:

The GitHub Actions workflow that is used in this repo, .github/workflows/update-best-of-list.yml is from the [best-of(https://github.com/best-of-lists/best-of) project, which also contains the template from which new best-of lists, like this one, can be generated. It copies the original update-best-of-list.yml, from here. It uses the best-of-update-action, which in turn uses the Python code from the best-of-generator package to turn a projects.yaml into a README.md.

The best-of project has been updated recently (2024), but not the other components, which are actually used for updating this list. The original update-best-of-list.yml in the template has not been updated since 2022, the action since 2022, and the generator even since 2021.

In #345, I created personal forks of the latter two, for debugging purposes only.

In this project, the switch to use either the official or the personal fork action, is here (permalink).

If the official projects being unmaintained, the likelihood that they will break at some point increases. Or if major configuration changes are undertaken for this list. In that case, the procedure done in #345 can be adapted for that.

This issue for listing possible current or future concerns that advocate for switching to such a self-maintained version of the update-cation and the best-of-generator.

@Irratzo Irratzo added the configuration Issue refers to the best-of list configuration label Aug 15, 2024
@Irratzo Irratzo changed the title Switch to self-maintained workflow Arguments for switching to self-maintained update workflow Aug 15, 2024
@Irratzo
Copy link
Member Author

Irratzo commented Aug 15, 2024

Argument 1) for switching to self-maintained update-best-of-list worfklow.

Deprecation warnings. For example, here.

Annotations

5 warnings

update-best-of-list

The following actions uses node12 which is deprecated and will be forced to run on node16: actions/create-release@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
update-best-of-list

The following actions use a deprecated Node.js version and will be forced to run on node20: stefanzweifel/git-auto-commit-action@v4, actions/create-release@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
update-best-of-list

The set-output command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
update-best-of-list

The set-output command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
update-best-of-list

The set-output command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
configuration Issue refers to the best-of list configuration
Projects
None yet
Development

No branches or pull requests

1 participant