AURO MIGRATION: Update node to v22

[jason-capsule42]

Resolves AlaskaAirlines/auro-templates#6

Summary by Sourcery

Update Node to v22 and migrate to Auro library v3.

Enhancements:

• Remove graphiteWidth option for performance reasons.
• Update repository settings to remove description and update topics.
• Update team permissions to grant admin access to auro-team and push access to nonauroteamwriteaccess.
• Update contributing guidelines with information about conventional commits and rebasing.
• Add a workflow to deploy a demo on pull requests to the main branch.

Build:

• Update Node version to v22 in the project configuration.

CI:

• Update CI workflows to test against Node 20 and 22.

Tests:

• Update test matrix in CI to include Node version 22.

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request updates the project to use Node.js v22 and introduces Conventional Commits.

Sequence diagram for updated PR workflow with Conventional Commits

sequenceDiagram
    actor Developer
    participant Git
    participant CI

    Developer->>Git: Create feature branch
    Developer->>Git: Make changes
    Developer->>Git: Commit with conventional format<br/>(type(scope): subject)
    Note over Developer,Git: Format: feat/fix/perf(scope): message
    Developer->>Git: Push changes
    Git->>CI: Trigger CI pipeline
    CI->>CI: Run tests on Node v20.x & v22.x
    CI-->>Developer: Return test results
    Note over Developer,CI: Tests must pass on both<br/>Node v20.x and v22.x

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. Updated the required Node.js version for tests to v22 in the settings file.	.github/workflows/testPublish.yml package.json .github/settings.yml
Introduced Conventional Commits	Added information about Conventional Commits and commit message formatting to the contributing guidelines.	.github/CONTRIBUTING.md
Added a workflow to publish a demo	Created a new workflow to publish a demo upon pull request merge.	.github/workflows/publishDemo.yml
Updated repository settings	Removed the repository description. Updated repository topics. Added team access settings.	.github/settings.yml
Updated contributing guidelines	Clarified the process for submitting issues and pull requests. Added information about rebasing and maintaining a linear repository history. Removed the requirement to run "npm i" before working on a project.	.github/CONTRIBUTING.md
Updated stale bot configuration	Added spacing between configuration options for better readability.	.github/stale.yml
Updated pull request template	Removed an unnecessary blank line.	.github/PULL_REQUEST_TEMPLATE.md
Updated CodeQL workflow	Removed unnecessary blank lines.	.github/workflows/codeql.yml
Updated code of conduct	Added line breaks for better readability.	.github/CODE_OF_CONDUCT.md

---

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.}

[sun-mota]

Needs #43

[DukeFerdinand]

Merging in without waiting for requirements. Reason: Node 18 is no longer a required action and will be replaced with node 20/22

[blackfalcon]

🎉 This PR is included in version 3.2.0 🎉

The release is available on:

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

Your semantic-release bot 📦🚀