Skip to content

fix: Handle the scenario where a package.json#browser field could be false #577

fix: Handle the scenario where a package.json#browser field could be false

fix: Handle the scenario where a package.json#browser field could be false #577

Triggered via pull request June 21, 2024 21:35
Status Failure
Total duration 11s
Artifacts

pr.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

1 error and 1 warning
lint
No release type found in pull request title "Handle the scenario where a package.json#browser field could be set t…". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/ Available types: - feat: A new feature - fix: A bug fix - docs: Documentation only changes - style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc) - refactor: A code change that neither fixes a bug nor adds a feature - perf: A code change that improves performance - test: Adding missing tests or correcting existing tests - build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm) - ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs) - chore: Other changes that don't modify src or test files - revert: Reverts a previous commit
lint
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: amannn/action-semantic-pull-request@0b14f54ac155d88e12522156e52cb6e397745cfd. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.