feat: Add JSON:API sparse fieldset relationship support #214
doomsporkAnnotations
1 error and 1 warning
|
Check Title
Pull Request title "Add JSON:API sparse fieldset relationship support" failed to match rule: /^(refactor!|feat!|fix!|refactor|fix|feat|chore)(\(\w+\))?:\s(\[#\d{1,5}\])?.*$/
Your PR title does not match the Conventional Commits convention. Please rename your PR to match one of the following formats:
fix: [#123] some title of the PR
fix(scope): [#123] some title of the PR
feat: [#1234] some title of the PR
chore: update some action
Note: Adding ! (i.e. `feat!:`) represents a breaking change and will result in a SemVer major release.
Please use one of the following types:
- **feat:** A new feature, resulting in a MINOR version bump.
- **fix:** A bug fix, resulting in a PATCH version bump.
- **refactor:** A code change that neither fixes a bug nor adds a feature.
- **chore:** Changes unrelated to the release code, resulting in no version bump.
- **revert:** Reverts a previous commit.
See https://www.conventionalcommits.org/en/v1.0.0/ for more information.
|
|
Check Title
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: beam-community/actions-pr-title@v1.0.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|