This issue defines a list of tasks that need to be performed in this repo to make sure it's ci/cd automation works long term without any issues.
It is up to maintainers to decide if it must be addressed in one or multiple PRs.
Below are 3 different sections describing 3 different important ci/cd changes.
IMPORTANT-START
For GitHub workflows that contain This workflow is centrally managed in https://github.com/asyncapi/.github/ you do not have to perform any work. These workflows were already updated through the update in .github. The only exception is the workflows related to nodejs release. More details in Upgrade Release pipeline - in case of nodejs projects section
IMPORTANT-END
Deprecation of way data is shared between steps
Every single GitHub Action workflow that has echo "::set-output name={name}::{value}" need to be updated to follow echo "{name}={value}" >> $GITHUB_OUTPUT
We do not yet know when set-output will stop working. Previous disable date was 31.05 but now then say community needs more time.
2nd bullet point is still relevant for you even if your projects in not nodejs project
Every single workflow that uses setup-node action needs an update to follow v3 version of this action, and make sure minimum node 14 is used
Now this part is more complex. Problem with node12 is that node-based GitHub Actions were using it in majority as a runtime environment. Look for example at this action.yaml file for setup-node action v2. So the job that you have to do is go through all the workflows, and verify every single action that you use, make sure you are using the latest version that is not based on node12. I already did review a lot of actions as part of this PR so maybe you will find some actions there and can copy from me. For example action/checkout needs to be updated to v3.
Node12 end of support in action is probably September 27th.
derberg
commented
1 year ago
This issue defines a list of tasks that need to be performed in this repo to make sure it's ci/cd automation works long term without any issues.
It is up to maintainers to decide if it must be addressed in one or multiple PRs.
Below are 3 different sections describing 3 different important ci/cd changes.
IMPORTANT-START For GitHub workflows that contain
This workflow is centrally managed in https://github.com/asyncapi/.github/you do not have to perform any work. These workflows were already updated through the update in.github. The only exception is the workflows related to nodejs release. More details in Upgrade Release pipeline - in case of nodejs projects section IMPORTANT-ENDDeprecation of way data is shared between steps
Every single GitHub Action workflow that has
echo "::set-output name={name}::{value}"need to be updated to followecho "{name}={value}" >> $GITHUB_OUTPUTWe do not yet know when
set-outputwill stop working. Previous disable date was 31.05 but now then say community needs more time.For more details read official article from GitHub
Deprecation of node12
v3version of this action, and make sure minimum node 14 is usednode12is that node-based GitHub Actions were using it in majority as a runtime environment. Look for example at this action.yaml file for setup-node action v2. So the job that you have to do is go through all the workflows, and verify every single action that you use, make sure you are using the latest version that is not based onnode12. I already did review a lot of actions as part of this PR so maybe you will find some actions there and can copy from me. For exampleaction/checkoutneeds to be updated to v3.Node12 end of support in action is probably September 27th.
For more details read official article from GitHub
Upgrade Release pipeline - in case of nodejs projects
You have 2 options. You can:
A. choose to switch to new release pipeline using instruction from https://github.com/asyncapi/.github/issues/205
B. stay with old release pipeline, and manually update GitHub workflows and actions used in it, you can inspire a lot from this PR https://github.com/asyncapi/.github/pull/226
I definitely recommend going with A
Workflows related to release: