AURO MIGRATION: Update node to v22

[jason-capsule42]

Resolves AlaskaAirlines/auro-templates#6

Summary by Sourcery

Update Node to v22 and revise contributing guidelines.

Build:

• Update Node to v22.

CI:

• Update CI to test against Node v20 and v22.

Documentation:

• Revise contributing guidelines, including updating issue and pull request templates, adding a rebase policy, clarifying commit message guidelines, and updating the code of conduct.

Tests:

• Update CI tests to Node v20 and v22.

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request updates the Auro project to use Node.js v22 and introduces several improvements to the contributing guidelines, issue templates, and CI/CD pipeline.

State diagram: Updated PR workflow states

stateDiagram-v2
    [*] --> IssueSubmitted
    IssueSubmitted --> UnderReview: Team reviews within 48h
    UnderReview --> Abandoned: Author unresponsive
    UnderReview --> Consultation: Team consultation
    Consultation --> Development: Approved to start work
    Development --> PullRequest: Submit PR
    PullRequest --> CodeReview: Team reviews
    CodeReview --> Merged: Approved
    CodeReview --> UpdateRequired: Changes needed
    UpdateRequired --> CodeReview: Updates submitted
    Merged --> [*]
    Abandoned --> [*]

Loading

File-Level Changes

Change	Details	Files
Updated Node.js version	Updated Node.js version to v22 in the test and publish workflow. Updated the engines section in package.json to reflect the new Node.js version. Regenerated package-lock.json to include updated dependencies for Node.js v22. Updated the test matrix in the settings.yml file to use Node.js v20 and v22.	.github/workflows/testPublish.yml package.json package-lock.json .github/settings.yml
Improved contributing guidelines	Added a link to the Innersourcing Flow Guide on Sharepoint for Alaska Airlines employees. Clarified the process for submitting issues and pull requests. Added a section on rebasing and why it's preferred over merging. Emphasized the importance of using conventional commits and provided examples. Added a section on Git commit messages and best practices.	.github/CONTRIBUTING.md
Updated issue templates	Added exit criteria to all issue templates. Updated the bug report template to request screenshots and clarify content. Updated labels in the issue templates to use double quotes.	.github/ISSUE_TEMPLATE/bug_report.yml .github/ISSUE_TEMPLATE/feature_request.yml .github/ISSUE_TEMPLATE/general-support.yml
Added a new workflow to publish a demo	Created a new workflow file to publish a demo upon pull request merge to the main branch. The workflow uses a reusable workflow from the AlaskaAirlines/auro-library repository. The workflow uses the AURO_SURGE_TOKEN secret to authenticate with Surge.	.github/workflows/publishDemo.yml
Updated CODEOWNERS file	Updated the CODEOWNERS file to reflect changes in team responsibilities. Specific details of the changes were not provided in the diff.	.github/CODEOWNERS
Updated other files	Updated the settings.yml file to include team permissions and update status checks. Updated the stale.yml file to include additional configuration options. Updated the pull request template to clarify the summary section and remove an unnecessary option. Updated the code of conduct file to remove specific contact information. Updated the codeql.yml file to remove unused queries.	.github/settings.yml .github/stale.yml .github/PULL_REQUEST_TEMPLATE.md .github/CODE_OF_CONDUCT.md .github/workflows/codeql.yml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time. You can also use
  this command to specify where the summary should be inserted.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[github-actions]

Surge demo deployment failed! 😭

[sourcery-ai]

Hey @jason-capsule42 - I've reviewed your changes and they look great!

Here's what I looked at during the review

• 🟢 General issues: all looks good
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟢 Complexity: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[rmenner]

Need to merge #370

[blackfalcon]

🎉 This PR is included in version 4.3.1 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀