CI/CD Workflows Need to use Stable Tag

[nutjob4life]

As part of our "lessons learned", having PDS repositories use the main branch of Roundup Action causes problems—namely, if a feature is implemented or a bug is fixed that introduces a new bug, every repository using main is affected.

Instead, when we have a point in the Roundup development that we consider stable, we tag it with stable. A workflow YAML file can say:

uses: NASA-PDS/roundup-action@stable

to say it prefers that tag of the action and not some other branch—especially not main.

The following repositories are still using the @main branch of the Roundup Action. These should should be transitioned to use @stable:

• [ ] api-search-query-lexer (awaiting merge)
• [ ] archive-analytics (awaiting merge)
• [ ] harvest (awaiting merge)
• [ ] pds-api-javalib (awaiting merge)
• [ ] pds-api-pythonlib (awaiting merge)
• [ ] pds-api-service (awaiting merge)
• [ ] pds-deep-archive (awaiting mrege)
• [ ] pds-doi-service (awaiting merge)
• [ ] pds-registry-app (awaiting merge)
• [ ] pds-registry-common (awaiting merge)
• [ ] pds-registry-mgr-elastic (awaiting merge)
• [ ] pds-template-repo-java (awaiting merge)
• [ ] pds-template-repo-python (awaiting merge)
• [ ] pds4-information-model (awaiting merge)
• [ ] pds4-jparser (awaiting merge)
• [ ] pdsen-maven-parent (awaiting merge)
• [ ] registry-api-service (awaiting merge)
• [ ] supplementer (awaiting merge)

[jordanpadams]

@nutjob4life oops! I may have jumped the gun here with validate and pds4-jparser. just realized we don't actually have a stable branch yet. once we have that, we can test this out.

[nutjob4life]

@jordanpadams we do indeed have @stable on roundup-action!

Also it's doubly-fine right now because roundup-action@main == roundup-action@stable 😌

[jordanpadams]

@nutjob4life copy. i was thinking i didn't see the branch but I see the tag 😨