AURO MIGRATION: Update node to v22

[jason-capsule42]

Resolves AlaskaAirlines/auro-templates#6

Summary by Sourcery

Update Node.js to version 22.

Build:

• Update Node engine to support versions 20 and 22.

CI:

• Update CI workflow to test on Node versions 20 and 22.

Documentation:

• Update contributing guidelines with information about rebasing, conventional commits, and issue/PR templates.

Tests:

• Update test matrix to include Node version 22.

[sourcery-ai]

Reviewer's Guide by Sourcery

This PR updates the project to use Node.js v22 and introduces several improvements to the contributing guidelines and repository settings.

State diagram: Updated issue lifecycle

stateDiagram-v2
    [*] --> Open: Issue created
    Open --> InProgress: Work started
    Open --> Stale: 30 days inactive
    Stale --> Closed: 7 days inactive
    InProgress --> Review: PR submitted
    Review --> Merged: PR approved
    Review --> InProgress: Changes requested
    Merged --> [*]

    note right of Open
        New requirement:
        Must consult team
        before starting work
    end note

    note right of Stale
        Updated stale bot
        configuration
    end note

Loading

File-Level Changes

Change	Details	Files
Updated Node.js version	Updated Node.js version to v22 in the test and publish workflow. Updated Node.js version to v22 in package.json. Regenerated package-lock.json. Updated the test matrix in settings.yml to use Node.js v20 and v22. Removed specific query from codeql.yml workflow.	.github/workflows/testPublish.yml package.json package-lock.json .github/settings.yml .github/workflows/codeql.yml
Improved contributing guidelines	Added guidance for Alaska Airlines employees, contractors, and vendors. Clarified feature request process. Updated issue submission guidelines. Added a 48-hour response time SLA for issue submissions. Added guidance on pull request submissions. Clarified feature branch naming conventions. Added a section on rebasing and avoiding git pull on feature branches. Added information on Conventional Commits and commit message formatting. Included examples of commit messages.	.github/CONTRIBUTING.md
Updated repository settings	Removed the repository description. Updated repository topics. Added team access settings. Updated stale bot configuration. Simplified pull request template. Updated code of conduct.	.github/settings.yml .github/CODEOWNERS .github/stale.yml .github/PULL_REQUEST_TEMPLATE.md .github/CODE_OF_CONDUCT.md
Added issue templates	Created a new bug report template. Updated the feature request template. Created a general support template.	.github/ISSUE_TEMPLATE/bug_report.yml .github/ISSUE_TEMPLATE/feature_request.yml .github/ISSUE_TEMPLATE/general-support.yml
Added demo publishing workflow	Created a workflow to publish demos on pull requests to the main branch.	.github/workflows/publishDemo.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: 1 issue found
• 🟢 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.}

[sourcery-ai]

issue (bug_risk): The condition had a logical error that could cause unintended releases

The original condition would always evaluate the second part as true. The fix using parentheses is correct: github.event_name == 'push' && (github.ref == 'refs/heads/main' || github.ref == 'refs/heads/beta')

[sun-mota]

Need #233

[blackfalcon]

🎉 This PR is included in version 4.3.0 🎉

The release is available on:

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

Your semantic-release bot 📦🚀