[Release] v0.13.4 #76
release.yml
on: push
release
3m 16s
update-config-schema
55s
Annotations
14 warnings
|
update-config-schema
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions-js/push@master, actions-rs/cargo@v1. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
update-config-schema
`codesnap` (lib) generated 4 warnings (run `cargo fix --lib -p codesnap` to apply 4 suggestions)
|
|
update-config-schema:
core/src/utils/highlight.rs#L25
hiding a lifetime that's elided elsewhere is confusing
|
|
update-config-schema:
core/src/components/highlight_code_block.rs#L86
hiding a lifetime that's elided elsewhere is confusing
|
|
update-config-schema:
core/src/ansi.rs#L20
hiding a lifetime that's elided elsewhere is confusing
|
|
update-config-schema:
core/src/utils/path.rs#L4
unused import: `var`
|
|
update-config-schema
/home/runner/work/codesnap/codesnap/core/Cargo.toml: unused manifest key: example.0.features
|
|
release
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions-rs/cargo@v1, mathieudutour/github-tag-action@v6.2, SebRollen/toml-action@v1.2.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
release
`codesnap` (lib) generated 4 warnings (run `cargo fix --lib -p codesnap` to apply 4 suggestions)
|
|
release
hiding a lifetime that's elided elsewhere is confusing
|
|
release
hiding a lifetime that's elided elsewhere is confusing
|
|
release
hiding a lifetime that's elided elsewhere is confusing
|
|
release
unused import: `var`
|
|
release
`cargo login <token>` is deprecated in favor of reading `<token>` from stdin
|