Create custom actions

[CalvinWilkinson]

Complete The Item Below

• I have updated the title without removing the 🚧 emoji.

Description

Create the following custom github actions for other projects in the KinsonDigital organization to take advantage of.

Note

These actions will each be a single TypeScript module that performs the work.

1. Create a close milestone action
2. Send X Announcement action
3. Get version action
4. Validate version action
5. Transpile readme action
6. Update copyright action
7. Nuget package exists action
8. Milestone exists action
9. All milestone issues closed action
10. GitHub release exists action
11. Validate .NET SDK version action
12. Validate tag action
13. Update the infrastructure release workflow to use the new custom actions

Acceptance Criteria

The items to complete to satisfy the Definition of Done.

• All the unit tests have been executed and passed locally after PR work is complete. (Why? Refer to 'Additional Information' below.)
• Close milestone custom action created
• Send X announcement custom action created
• Get version custom action created
• Validate version custom action created
• Transpile readme custom action created
• Update copyright custom action created
• Nuget package exists, custom action created
• Milestone exists custom action created
• All milestone items closed, custom action created
• GitHub release exists, custom action created
• Validate .NET SDK version custom action created
• Validate tag custom action created

Extra:

• For all github actions that need an owner and/or a repo value, validate that they both exist.
  • Refactor the Validators module functions to take in the repo owner and repo names as parameters.
• dotnet-lib-release.yml workflow updated to use new custom actions
• github-action-release.yml file updated to have a prerelease validation job that uses the new custom actions
• The infrastructure release workflow has been updated to use the new custom actions
• All github actions are updated to the latest versions
• Set all deno actions to enable caching for workflows.
  • For the release workflows, use a workflow input to use a default value of true and use it as a value to set the caching

ToDo Items

The items to complete to satisfy the Definition of Done.

• Add a priority label to the issue. Refer to the Priority Type Labels section below.
• Link the issue to the correct milestone (if applicable).

Code of Conduct

• I agree to follow this project's Code of Conduct.

[CalvinWilkinson]

Caution

The following breaking changes were introduced
The following dotnet-lib-release workflow inputs were removed and replaced:

1. Workflow inputs removed for dotnet-lib-release.yml workflow:
   • relative-release-notes-dir-path
   • release-notes-file-name-prefix
   • run-branch
   • pr-include-notes-label
2. Workflow inputs removed for dotnet-action-release.yml workflow:
   • relative-release-notes-dir-path
   • release-notes-file-name-prefix
   • run-branch
   • pr-include-notes-label
3. The workflow run-csharp-tests.yml has been removed.
   • This means that all projects that use this workflow will have to replace it with some equivalent.
4. The run_tests job has been removed from the dotnet-lib-release.yml workflow.
   • This means that any projects that use this workflow will not have tests executed. You will have to implement the test jobs/steps manually for dotnet library releases.
5. The run_tests job has been removed from the dotnet-action-release.yml workflow.
   • This means that any projects that use this workflow will not have tests executed. You will have to implement the test jobs/steps manually for dotnet library releases.
6. The docusaurus-release.yml workflow has been removed.
   • No projects in the organization use this.
7. The validate-tag.yml workflow has been removed.
   • No projects in the organization use this.
8. The org variable INFRASTRUCTURE_VERSION is now replacing the variable CICD_SCRIPTS_VERSION

The release-notes-file-path workflow input is a fully qualified file path to the release notes and is what replaces the relative-release-notes-dir-path and release-notes-file-name-prefix workflow inputs.

[CalvinWilkinson]

Note

Added workflow inputs below:

1. Workflow inputs added to dotnet-lib-release.yml
   • release-notes-file-path - Fully qualified path. It is the consumer's responsibility to build the path now.
   • deno-version - The version of deno to use. This input is replacing all of the DENO_VERSION variable references
   • enable-deno-cache - Default is true, but now uses caching for deno scripts.
2. Workflow inputs added to dotnet-action-release.yml
   • release-notes-file-path - Fully qualified path. It is the consumer's responsibility to build the path now.
   • deno-version - The version of deno to use. This input is replacing all of the DENO_VERSION variable references
   • enable-deno-cache - Default is true, but now uses caching for deno scripts.