Error: To https://github.com/putoutjs/printer ! refs/heads/master:refs/heads/master [rejected] (fetch first) Done Pushing to https://github.com/putoutjs/printer POST git-receive-pack (57 bytes) error: failed to push some refs to 'https://github.com/putoutjs/printer' hint: Updates were rejected because the remote contains work that you do not hint: have locally. This is usually caused by another repository pushing to hint: the same ref. If you want to integrate the remote changes, use hint: 'git pull' before pushing again. hint: See the 'Note about fast-forwards' in 'git push --help' for details.

Error: To https://github.com/putoutjs/printer ! refs/heads/master:refs/heads/master [rejected] (fetch first) Done Pushing to https://github.com/putoutjs/printer POST git-receive-pack (57 bytes) error: failed to push some refs to 'https://github.com/putoutjs/printer' hint: Updates were rejected because the remote contains work that you do not hint: have locally. This is usually caused by another repository pushing to hint: the same ref. If you want to integrate the remote changes, use hint: 'git pull' before pushing again. hint: See the 'Note about fast-forwards' in 'git push --help' for details.

Error: To https://github.com/putoutjs/printer ! refs/heads/master:refs/heads/master [rejected] (non-fast-forward) Done Pushing to https://github.com/putoutjs/printer error: failed to push some refs to 'https://github.com/putoutjs/printer' hint: Updates were rejected because the tip of your current branch is behind hint: its remote counterpart. If you want to integrate the remote changes, hint: use 'git pull' before pushing again. hint: See the 'Note about fast-forwards' in 'git push --help' for details.

Error: To https://github.com/putoutjs/printer ! refs/heads/master:refs/heads/master [rejected] (non-fast-forward) Done Pushing to https://github.com/putoutjs/printer error: failed to push some refs to 'https://github.com/putoutjs/printer' hint: Updates were rejected because the tip of your current branch is behind hint: its remote counterpart. If you want to integrate the remote changes, hint: use 'git pull' before pushing again. hint: See the 'Note about fast-forwards' in 'git push --help' for details.

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: EndBug/add-and-commit@v9. 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: EndBug/add-and-commit@v9. 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/