build(deps): bump @glideapps/ts-necessities from 2.2.3 to 2.4.0

[dependabot]

Bumps @glideapps/ts-necessities from 2.2.3 to 2.4.0.

Changelog

Sourced from @​glideapps/ts-necessities's changelog.

Release Process

This document explains how to release new versions of @glideapps/ts-necessities to NPM.

GitHub Actions Workflows

The repository uses two main GitHub Actions workflows:

1. CI Workflow (ci.yml)

   • Runs on every push to main and on pull requests
   • Runs on Node.js 20.x and 22.x
   • Performs build, lint, and test operations
   • Verifies dual module compatibility (CJS and ESM)

2. Publish Workflow (publish.yml)

   • Triggers automatically when a GitHub release is created
   • Builds, tests, and publishes the package to NPM
   • Verifies that the package version matches the GitHub release tag
   • Uses the NPM_TOKEN secret for authentication

Making a Release

Prerequisites

• Ensure you have write access to the GitHub repository
• Make sure the NPM_TOKEN secret is set up in the repository settings
  • Go to Settings → Secrets and variables → Actions
  • The token should have permission to publish to the @glideapps organization

Steps to Release

1. Update Package Version

   • Update the version field in package.json
   • Commit and push the change to main

2. Create a GitHub Release

   • Go to the repository on GitHub
   • Navigate to Releases → "Create a new release"
   • Create a new tag (e.g., v2.4.0 - must match the version in package.json)
   • Add a title and description for the release
   • Click "Publish release"

3. Automatic Publishing

   • The publish.yml workflow will automatically trigger
   • It will verify the version matches the tag
   • If tests pass, it will publish to NPM

4. Verify the Release

   • Check the Actions tab to ensure the workflow completed successfully
   • Verify the package is available on NPM with the new version

... (truncated)

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.