Mirrors/nushell
2
0
Fork 0
mirror of https://github.com/nushell/nushell synced 2024-12-30 23:08:56 +00:00
Code Issues Projects Releases Packages Wiki Activity
nushell/.github/workflows/release.yml

204 lines
5.7 KiB
YAML
Raw Normal View History

feat: Refactor and optimize the github release workflow: deliver binary package for more targets (#5649)
2022-05-28 02:41:47 +00:00
#
# REF:
# 1. https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstrategymatrixinclude
#
Add release automation with GitHub Actions (#2048)
2020-06-24 23:43:25 +00:00
name: Create Release Draft
on:
update release to allow running manually (#4123)
2021-11-15 20:04:00 +00:00
workflow_dispatch:
Add release automation with GitHub Actions (#2048)
2020-06-24 23:43:25 +00:00
push:
bye bye upx, let's try stripping alone (#4172)
2021-11-30 18:11:01 +00:00
tags: ["[0-9]+.[0-9]+.[0-9]+*"]
Add release automation with GitHub Actions (#2048)
2020-06-24 23:43:25 +00:00
feat: Refactor and optimize the github release workflow: deliver binary package for more targets (#5649)
2022-05-28 02:41:47 +00:00
defaults:
run:
shell: bash
updated to include less and nushell licenses (#2085)
2020-06-30 22:45:42 +00:00
feat: Refactor and optimize the github release workflow: deliver binary package for more targets (#5649)
2022-05-28 02:41:47 +00:00
jobs:
Add full releases of Nu binaries along with the standard releases (#10457) # Description Add full releases of Nu binaries along with the standard releases, close: https://github.com/nushell/nushell/issues/10322 A full release means: 1. Build with `--features=dataframe,extra` flag 2. Contains `-full` in the package name ### **A test release could be found in the nushell/nightly Repo: https://github.com/nushell/nightly/releases/tag/v0.85.1** The action running log: https://github.com/nushell/nightly/actions/runs/6260611553 # User-Facing Changes Will attach the following release packages along with the official ones as before: 1. nu-*-aarch64-darwin-full.tar.gz 2. nu-*-aarch64-linux-gnu-full.tar.gz 3. nu-*-aarch64-windows-msvc-full.msi 4. nu-*-aarch64-windows-msvc-full.zip 5. nu-*-x86_64-darwin-full.tar.gz 6. nu-*-x86_64-linux-gnu-full.tar.gz 7. nu-*-x86_64-linux-musl-full.tar.gz 8. nu-*-x86_64-windows-msvc-full.msi 9. nu-*-x86_64-windows-msvc-full.zip
2023-09-23 01:41:08 +00:00
standard:
name: Std
feat: Refactor and optimize the github release workflow: deliver binary package for more targets (#5649)
2022-05-28 02:41:47 +00:00
strategy:
Tweak release workflow after `0.92.1` lessons (#12401) Encountered repeated build failure that vanished after clearing the existing build caches. - Don't `fail-fast` (this is highly annoying, if a severe problem is detected, there is still the possibility to intervene manually) - Don't cache the build process, we do it rarely so any potential speed-up is offset by the uncertainty if this affects the artefact
2024-04-06 02:20:01 +00:00
fail-fast: false
feat: Refactor and optimize the github release workflow: deliver binary package for more targets (#5649)
2022-05-28 02:41:47 +00:00
matrix:
target:
- aarch64-apple-darwin
- x86_64-apple-darwin
- x86_64-pc-windows-msvc
Add aarch64-pc-windows-msvc building target for nu binaries (#9162)
2023-05-20 12:50:38 +00:00
- aarch64-pc-windows-msvc
feat: Refactor and optimize the github release workflow: deliver binary package for more targets (#5649)
2022-05-28 02:41:47 +00:00
- x86_64-unknown-linux-gnu
- x86_64-unknown-linux-musl
- aarch64-unknown-linux-gnu
Fix release workflows (#9542)
2023-06-28 01:15:32 +00:00
- armv7-unknown-linux-gnueabihf
Upgrade openssl-src to fix riscv64 target building error (#11861) Upgrade openssl-src to fix riscv64 target building error Workflow Test: https://github.com/nushell/nightly/actions/runs/7914366860
2024-02-15 13:05:50 +00:00
- riscv64gc-unknown-linux-gnu
feat: Refactor and optimize the github release workflow: deliver binary package for more targets (#5649)
2022-05-28 02:41:47 +00:00
extra: ['bin']
include:
- target: aarch64-apple-darwin
os: macos-latest
target_rustflags: ''
- target: x86_64-apple-darwin
os: macos-latest
target_rustflags: ''
- target: x86_64-pc-windows-msvc
extra: 'bin'
os: windows-latest
target_rustflags: ''
- target: x86_64-pc-windows-msvc
extra: msi
os: windows-latest
target_rustflags: ''
Add aarch64-pc-windows-msvc building target for nu binaries (#9162)
2023-05-20 12:50:38 +00:00
- target: aarch64-pc-windows-msvc
extra: 'bin'
os: windows-latest
target_rustflags: ''
- target: aarch64-pc-windows-msvc
extra: msi
os: windows-latest
target_rustflags: ''
feat: Refactor and optimize the github release workflow: deliver binary package for more targets (#5649)
2022-05-28 02:41:47 +00:00
- target: x86_64-unknown-linux-gnu
Update release script to nu v0.71 and use ubuntu-20.04 to build nu binary (#7290) # Description 1. Update nu to v0.71 for release script 2. Remove the usage of `set-output` see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/ 3. Use `ubuntu-20.04` instead of `ubuntu-latest` to fix #7282 To check the workflow running result see: https://github.com/hustcer/nu-release/actions/runs/3588720720/jobs/6040412953 # User-Facing Changes _(List of all changes that impact the user experience here. This helps us keep track of breaking changes.)_ # Tests + Formatting Don't forget to add tests that cover your changes. Make sure you've run and fixed any issues with these commands: - `cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - `cargo clippy --workspace -- -D warnings -D clippy::unwrap_used -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # After Submitting If your PR had any user-facing changes, update [the documentation](https://github.com/nushell/nushell.github.io) after the PR is merged, if necessary. This will help us keep the docs up to date.
2022-12-01 02:44:21 +00:00
os: ubuntu-20.04
feat: Refactor and optimize the github release workflow: deliver binary package for more targets (#5649)
2022-05-28 02:41:47 +00:00
target_rustflags: ''
- target: x86_64-unknown-linux-musl
Update release script to nu v0.71 and use ubuntu-20.04 to build nu binary (#7290) # Description 1. Update nu to v0.71 for release script 2. Remove the usage of `set-output` see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/ 3. Use `ubuntu-20.04` instead of `ubuntu-latest` to fix #7282 To check the workflow running result see: https://github.com/hustcer/nu-release/actions/runs/3588720720/jobs/6040412953 # User-Facing Changes _(List of all changes that impact the user experience here. This helps us keep track of breaking changes.)_ # Tests + Formatting Don't forget to add tests that cover your changes. Make sure you've run and fixed any issues with these commands: - `cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - `cargo clippy --workspace -- -D warnings -D clippy::unwrap_used -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # After Submitting If your PR had any user-facing changes, update [the documentation](https://github.com/nushell/nushell.github.io) after the PR is merged, if necessary. This will help us keep the docs up to date.
2022-12-01 02:44:21 +00:00
os: ubuntu-20.04
feat: Refactor and optimize the github release workflow: deliver binary package for more targets (#5649)
2022-05-28 02:41:47 +00:00
target_rustflags: ''
- target: aarch64-unknown-linux-gnu
Update release script to nu v0.71 and use ubuntu-20.04 to build nu binary (#7290) # Description 1. Update nu to v0.71 for release script 2. Remove the usage of `set-output` see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/ 3. Use `ubuntu-20.04` instead of `ubuntu-latest` to fix #7282 To check the workflow running result see: https://github.com/hustcer/nu-release/actions/runs/3588720720/jobs/6040412953 # User-Facing Changes _(List of all changes that impact the user experience here. This helps us keep track of breaking changes.)_ # Tests + Formatting Don't forget to add tests that cover your changes. Make sure you've run and fixed any issues with these commands: - `cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - `cargo clippy --workspace -- -D warnings -D clippy::unwrap_used -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # After Submitting If your PR had any user-facing changes, update [the documentation](https://github.com/nushell/nushell.github.io) after the PR is merged, if necessary. This will help us keep the docs up to date.
2022-12-01 02:44:21 +00:00
os: ubuntu-20.04
feat: Refactor and optimize the github release workflow: deliver binary package for more targets (#5649)
2022-05-28 02:41:47 +00:00
target_rustflags: ''
Fix release workflows (#9542)
2023-06-28 01:15:32 +00:00
- target: armv7-unknown-linux-gnueabihf
os: ubuntu-20.04
Update build flags for riscv64gc and armv7 targets (#10564) Update build flags for riscv64gc and armv7 targets， as they are not required any more, let's give it a try in nightly release
2023-10-01 01:32:34 +00:00
target_rustflags: ''
Upgrade openssl-src to fix riscv64 target building error (#11861) Upgrade openssl-src to fix riscv64 target building error Workflow Test: https://github.com/nushell/nightly/actions/runs/7914366860
2024-02-15 13:05:50 +00:00
- target: riscv64gc-unknown-linux-gnu
os: ubuntu-latest
target_rustflags: ''
feat: Refactor and optimize the github release workflow: deliver binary package for more targets (#5649)
2022-05-28 02:41:47 +00:00
runs-on: ${{matrix.os}}
Add release automation with GitHub Actions (#2048)
2020-06-24 23:43:25 +00:00
steps:
Bump actions/checkout from 4.1.4 to 4.1.5 (#12804) Bumps [actions/checkout](https://github.com/actions/checkout) from 4.1.4 to 4.1.5. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/actions/checkout/releases">actions/checkout's releases</a>.</em></p> <blockquote> <h2>v4.1.5</h2> <h2>What's Changed</h2> <ul> <li>Update NPM dependencies by <a href="https://github.com/cory-miller"><code>@​cory-miller</code></a> in <a href="https://redirect.github.com/actions/checkout/pull/1703">actions/checkout#1703</a></li> <li>Bump github/codeql-action from 2 to 3 by <a href="https://github.com/dependabot"><code>@​dependabot</code></a> in <a href="https://redirect.github.com/actions/checkout/pull/1694">actions/checkout#1694</a></li> <li>Bump actions/setup-node from 1 to 4 by <a href="https://github.com/dependabot"><code>@​dependabot</code></a> in <a href="https://redirect.github.com/actions/checkout/pull/1696">actions/checkout#1696</a></li> <li>Bump actions/upload-artifact from 2 to 4 by <a href="https://github.com/dependabot"><code>@​dependabot</code></a> in <a href="https://redirect.github.com/actions/checkout/pull/1695">actions/checkout#1695</a></li> <li>README: Suggest <code>user.email</code> to be <code>41898282+github-actions[bot]@users.noreply.github.com</code> by <a href="https://github.com/cory-miller"><code>@​cory-miller</code></a> in <a href="https://redirect.github.com/actions/checkout/pull/1707">actions/checkout#1707</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/actions/checkout/compare/v4.1.4...v4.1.5">https://github.com/actions/checkout/compare/v4.1.4...v4.1.5</a></p> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/actions/checkout/blob/main/CHANGELOG.md">actions/checkout's changelog</a>.</em></p> <blockquote> <h1>Changelog</h1> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/actions/checkout/commit/44c2b7a8a4ea60a981eaca3cf939b5f4305c123b"><code>44c2b7a</code></a> README: Suggest <code>user.email</code> to be `41898282+github-actions[bot]<a href="https://github.com/users"><code>@​users</code></a>.norepl...</li> <li><a href="https://github.com/actions/checkout/commit/8459bc0c7e3759cdf591f513d9f141a95fef0a8f"><code>8459bc0</code></a> Bump actions/upload-artifact from 2 to 4 (<a href="https://redirect.github.com/actions/checkout/issues/1695">#1695</a>)</li> <li><a href="https://github.com/actions/checkout/commit/3f603f6d5e9f40714f97b2f017aa0df2a443192a"><code>3f603f6</code></a> Bump actions/setup-node from 1 to 4 (<a href="https://redirect.github.com/actions/checkout/issues/1696">#1696</a>)</li> <li><a href="https://github.com/actions/checkout/commit/fd084cde189b7b76ec305d52e27be545a0172823"><code>fd084cd</code></a> Bump github/codeql-action from 2 to 3 (<a href="https://redirect.github.com/actions/checkout/issues/1694">#1694</a>)</li> <li><a href="https://github.com/actions/checkout/commit/9c1e94e0ad997d618b6113a2171b055037589028"><code>9c1e94e</code></a> Update NPM dependencies (<a href="https://redirect.github.com/actions/checkout/issues/1703">#1703</a>)</li> <li>See full diff in <a href="https://github.com/actions/checkout/compare/v4.1.4...v4.1.5">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=actions/checkout&package-manager=github_actions&previous-version=4.1.4&new-version=4.1.5)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> 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) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2024-05-08 02:35:08 +00:00
- uses: actions/checkout@v4.1.5
feat: Refactor and optimize the github release workflow: deliver binary package for more targets (#5649)
2022-05-28 02:41:47 +00:00
Remove inactive actions-rs/toolchain@v1.0.6 for release workflow (#7302) # Description Remove inactive actions-rs/toolchain@v1.0.6 for release workflow, https://github.com/actions-rs/toolchain is inactive for more than two years, and have lots of unfixed warnings: https://github.com/actions-rs/toolchain/issues?q=is%3Aissue+is%3Aopen+warning After this PR: Workflow running result: https://github.com/hustcer/nu-release/actions/runs/3590194180 Release Test: https://github.com/hustcer/nu-release/releases/tag/v0.72.7
2022-12-01 08:30:25 +00:00
- name: Update Rust Toolchain Target
run: |
echo "targets = ['${{matrix.target}}']" >> rust-toolchain.toml
Use setup-rust-toolchain for release workflow (#7315) # Description Use setup-rust-toolchain for release workflow to inline with the CI workflow Test workflow: https://github.com/hustcer/nu-release/actions/runs/3598316520 Demo Release: https://github.com/hustcer/nu-release/releases/tag/v0.72.8
2022-12-02 03:23:29 +00:00
Tweak release workflow after `0.92.1` lessons (#12401) Encountered repeated build failure that vanished after clearing the existing build caches. - Don't `fail-fast` (this is highly annoying, if a severe problem is detected, there is still the possibility to intervene manually) - Don't cache the build process, we do it rarely so any potential speed-up is offset by the uncertainty if this affects the artefact
2024-04-06 02:20:01 +00:00
- name: Setup Rust toolchain
Bump actions-rust-lang/setup-rust-toolchain from 1.6.0 to 1.8.0 (#11539) Bumps [actions-rust-lang/setup-rust-toolchain](https://github.com/actions-rust-lang/setup-rust-toolchain) from 1.6.0 to 1.8.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/actions-rust-lang/setup-rust-toolchain/releases">actions-rust-lang/setup-rust-toolchain's releases</a>.</em></p> <blockquote> <h2>v1.8.0</h2> <ul> <li>Allow specifying subdirectories for cache.</li> <li>Fix toolchain file overriding.</li> </ul> <h2>v1.7.0</h2> <h2>What's Changed</h2> <ul> <li>Allow overriding the toolchain file by <a href="https://github.com/Twey"><code>@​Twey</code></a> in <a href="https://redirect.github.com/actions-rust-lang/setup-rust-toolchain/pull/26">actions-rust-lang/setup-rust-toolchain#26</a></li> <li>ci: update checked rust-toolchain version by <a href="https://github.com/robjtede"><code>@​robjtede</code></a> in <a href="https://redirect.github.com/actions-rust-lang/setup-rust-toolchain/pull/29">actions-rust-lang/setup-rust-toolchain#29</a></li> <li>Prepare 1.7.0 release by <a href="https://github.com/robjtede"><code>@​robjtede</code></a> in <a href="https://redirect.github.com/actions-rust-lang/setup-rust-toolchain/pull/30">actions-rust-lang/setup-rust-toolchain#30</a></li> </ul> <h2>New Contributors</h2> <ul> <li><a href="https://github.com/Twey"><code>@​Twey</code></a> made their first contribution in <a href="https://redirect.github.com/actions-rust-lang/setup-rust-toolchain/pull/26">actions-rust-lang/setup-rust-toolchain#26</a></li> <li><a href="https://github.com/robjtede"><code>@​robjtede</code></a> made their first contribution in <a href="https://redirect.github.com/actions-rust-lang/setup-rust-toolchain/pull/29">actions-rust-lang/setup-rust-toolchain#29</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/actions-rust-lang/setup-rust-toolchain/compare/v1.6...v1.7.0">https://github.com/actions-rust-lang/setup-rust-toolchain/compare/v1.6...v1.7.0</a></p> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/actions-rust-lang/setup-rust-toolchain/blob/main/CHANGELOG.md">actions-rust-lang/setup-rust-toolchain's changelog</a>.</em></p> <blockquote> <h2>[1.8.0] - 2024-01-13</h2> <ul> <li>Allow specifying subdirectories for cache.</li> <li>Fix toolchain file overriding.</li> </ul> <h2>[1.7.0] - 2024-01-11</h2> <ul> <li>Allow overriding the toolchain file with explicit <code>toolchain</code> input. (<a href="https://redirect.github.com/actions-rust-lang/setup-rust-toolchain/issues/26">#26</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/actions-rust-lang/setup-rust-toolchain/commit/b113a30d27a8e59c969077c0a0168cc13dab5ffc"><code>b113a30</code></a> Merge pull request <a href="https://redirect.github.com/actions-rust-lang/setup-rust-toolchain/issues/34">#34</a> from actions-rust-lang/rel-180</li> <li><a href="https://github.com/actions-rust-lang/setup-rust-toolchain/commit/039765bd186526e4d2e1b2f3ec14f5216b4d92bc"><code>039765b</code></a> chore: prepare release 1.8.0</li> <li><a href="https://github.com/actions-rust-lang/setup-rust-toolchain/commit/84e65ce3155f72bc64fcd3fbc1eab7814e937925"><code>84e65ce</code></a> Merge pull request <a href="https://redirect.github.com/actions-rust-lang/setup-rust-toolchain/issues/32">#32</a> from gruebel/add-workspaces</li> <li><a href="https://github.com/actions-rust-lang/setup-rust-toolchain/commit/6f719a240eaaea9ba9c138657ae60ae23314e892"><code>6f719a2</code></a> Merge branch 'main' into add-workspaces</li> <li><a href="https://github.com/actions-rust-lang/setup-rust-toolchain/commit/15d0afaad9a057d55c8c95034bfb3aacb990a6b0"><code>15d0afa</code></a> ci: fix cache test</li> <li><a href="https://github.com/actions-rust-lang/setup-rust-toolchain/commit/922cc935eba0313aadf10debf4b777609f674024"><code>922cc93</code></a> ci: add cache-workspaces test</li> <li><a href="https://github.com/actions-rust-lang/setup-rust-toolchain/commit/bcda41b18de1f885ca4a1ccfc0cd120c57bfe9ca"><code>bcda41b</code></a> Merge pull request <a href="https://redirect.github.com/actions-rust-lang/setup-rust-toolchain/issues/33">#33</a> from fprasx/fprasx/fix-toolchain-overrides</li> <li><a href="https://github.com/actions-rust-lang/setup-rust-toolchain/commit/ba41ca6f71dca3d3a627600631fedb7f260d083e"><code>ba41ca6</code></a> ci: clearer test names</li> <li><a href="https://github.com/actions-rust-lang/setup-rust-toolchain/commit/aa089182f268c0255577cdc57a82a9b0819d59c3"><code>aa08918</code></a> ci: fix conditional</li> <li><a href="https://github.com/actions-rust-lang/setup-rust-toolchain/commit/c6086ae6e539b9cca10fba3642fe77e559ba5705"><code>c6086ae</code></a> test: add toolchain file override test</li> <li>Additional commits viewable in <a href="https://github.com/actions-rust-lang/setup-rust-toolchain/compare/v1.6.0...v1.8.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=actions-rust-lang/setup-rust-toolchain&package-manager=github_actions&previous-version=1.6.0&new-version=1.8.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> 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) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2024-01-15 02:27:41 +00:00
uses: actions-rust-lang/setup-rust-toolchain@v1.8.0
Fix winget release submission error (#10757) <!-- if this PR closes one or more issues, you can automatically link the PR with them by using one of the [*linking keywords*](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword), e.g. - this PR should close #xxxx - fixes #xxxx you can also mention related issues, PRs or discussions! --> # Description <!-- Thank you for improving Nushell. Please, check our [contributing guide](../CONTRIBUTING.md) and talk to the core team before making major changes. Description of your pull request goes here. **Provide examples and/or screenshots** if your changes affect the user experience. --> Fix winget release submission error, more details could be found here: https://github.com/nushell/nushell/pull/5812#issuecomment-1768294811 @fdncred @wolimst # User-Facing Changes <!-- List of all changes that impact the user experience here. This helps us keep track of breaking changes. --> # Tests + Formatting <!-- Don't forget to add tests that cover your changes. Make sure you've run and fixed any issues with these commands: - `cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - `cargo clippy --workspace -- -D warnings -D clippy::unwrap_used` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass (on Windows make sure to [enable developer mode](https://learn.microsoft.com/en-us/windows/apps/get-started/developer-mode-features-and-debugging)) - `cargo run -- -c "use std testing; testing run-tests --path crates/nu-std"` to run the tests for the standard library > **Note** > from `nushell` you can also use the `toolkit` as follows > ```bash > use toolkit.nu # or use an `env_change` hook to activate it automatically > toolkit check pr > ``` --> # After Submitting <!-- If your PR had any user-facing changes, update [the documentation](https://github.com/nushell/nushell.github.io) after the PR is merged, if necessary. This will help us keep the docs up to date. --> --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-10-18 18:00:19 +00:00
# WARN: Keep the rustflags to prevent from the winget submission error: `CAQuietExec: Error 0xc0000135`
with:
Tweak release workflow after `0.92.1` lessons (#12401) Encountered repeated build failure that vanished after clearing the existing build caches. - Don't `fail-fast` (this is highly annoying, if a severe problem is detected, there is still the possibility to intervene manually) - Don't cache the build process, we do it rarely so any potential speed-up is offset by the uncertainty if this affects the artefact
2024-04-06 02:20:01 +00:00
cache: false
Fix winget release submission error (#10757) <!-- if this PR closes one or more issues, you can automatically link the PR with them by using one of the [*linking keywords*](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword), e.g. - this PR should close #xxxx - fixes #xxxx you can also mention related issues, PRs or discussions! --> # Description <!-- Thank you for improving Nushell. Please, check our [contributing guide](../CONTRIBUTING.md) and talk to the core team before making major changes. Description of your pull request goes here. **Provide examples and/or screenshots** if your changes affect the user experience. --> Fix winget release submission error, more details could be found here: https://github.com/nushell/nushell/pull/5812#issuecomment-1768294811 @fdncred @wolimst # User-Facing Changes <!-- List of all changes that impact the user experience here. This helps us keep track of breaking changes. --> # Tests + Formatting <!-- Don't forget to add tests that cover your changes. Make sure you've run and fixed any issues with these commands: - `cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - `cargo clippy --workspace -- -D warnings -D clippy::unwrap_used` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass (on Windows make sure to [enable developer mode](https://learn.microsoft.com/en-us/windows/apps/get-started/developer-mode-features-and-debugging)) - `cargo run -- -c "use std testing; testing run-tests --path crates/nu-std"` to run the tests for the standard library > **Note** > from `nushell` you can also use the `toolkit` as follows > ```bash > use toolkit.nu # or use an `env_change` hook to activate it automatically > toolkit check pr > ``` --> # After Submitting <!-- If your PR had any user-facing changes, update [the documentation](https://github.com/nushell/nushell.github.io) after the PR is merged, if necessary. This will help us keep the docs up to date. --> --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-10-18 18:00:19 +00:00
rustflags: ''
Add full releases of Nu binaries along with the standard releases (#10457) # Description Add full releases of Nu binaries along with the standard releases, close: https://github.com/nushell/nushell/issues/10322 A full release means: 1. Build with `--features=dataframe,extra` flag 2. Contains `-full` in the package name ### **A test release could be found in the nushell/nightly Repo: https://github.com/nushell/nightly/releases/tag/v0.85.1** The action running log: https://github.com/nushell/nightly/actions/runs/6260611553 # User-Facing Changes Will attach the following release packages along with the official ones as before: 1. nu-*-aarch64-darwin-full.tar.gz 2. nu-*-aarch64-linux-gnu-full.tar.gz 3. nu-*-aarch64-windows-msvc-full.msi 4. nu-*-aarch64-windows-msvc-full.zip 5. nu-*-x86_64-darwin-full.tar.gz 6. nu-*-x86_64-linux-gnu-full.tar.gz 7. nu-*-x86_64-linux-musl-full.tar.gz 8. nu-*-x86_64-windows-msvc-full.msi 9. nu-*-x86_64-windows-msvc-full.zip
2023-09-23 01:41:08 +00:00
- name: Setup Nushell
Upgrade hustcer/setup-nu to v3.10 to fix macOS arm64 build errors (#12681) Upgrade hustcer/setup-nu to [v3.10](https://github.com/hustcer/setup-nu/releases/tag/v3.10) to fix macOS arm64 build errors Release Testing: https://github.com/nushell/nightly/actions/runs/8856404620
2024-04-27 02:18:08 +00:00
uses: hustcer/setup-nu@v3.10
Add full releases of Nu binaries along with the standard releases (#10457) # Description Add full releases of Nu binaries along with the standard releases, close: https://github.com/nushell/nushell/issues/10322 A full release means: 1. Build with `--features=dataframe,extra` flag 2. Contains `-full` in the package name ### **A test release could be found in the nushell/nightly Repo: https://github.com/nushell/nightly/releases/tag/v0.85.1** The action running log: https://github.com/nushell/nightly/actions/runs/6260611553 # User-Facing Changes Will attach the following release packages along with the official ones as before: 1. nu-*-aarch64-darwin-full.tar.gz 2. nu-*-aarch64-linux-gnu-full.tar.gz 3. nu-*-aarch64-windows-msvc-full.msi 4. nu-*-aarch64-windows-msvc-full.zip 5. nu-*-x86_64-darwin-full.tar.gz 6. nu-*-x86_64-linux-gnu-full.tar.gz 7. nu-*-x86_64-linux-musl-full.tar.gz 8. nu-*-x86_64-windows-msvc-full.msi 9. nu-*-x86_64-windows-msvc-full.zip
2023-09-23 01:41:08 +00:00
with:
Upgrade Nu to v0.93.0 for nightly and release workflow (#12721)
2024-05-02 03:11:53 +00:00
version: 0.93.0
Add full releases of Nu binaries along with the standard releases (#10457) # Description Add full releases of Nu binaries along with the standard releases, close: https://github.com/nushell/nushell/issues/10322 A full release means: 1. Build with `--features=dataframe,extra` flag 2. Contains `-full` in the package name ### **A test release could be found in the nushell/nightly Repo: https://github.com/nushell/nightly/releases/tag/v0.85.1** The action running log: https://github.com/nushell/nightly/actions/runs/6260611553 # User-Facing Changes Will attach the following release packages along with the official ones as before: 1. nu-*-aarch64-darwin-full.tar.gz 2. nu-*-aarch64-linux-gnu-full.tar.gz 3. nu-*-aarch64-windows-msvc-full.msi 4. nu-*-aarch64-windows-msvc-full.zip 5. nu-*-x86_64-darwin-full.tar.gz 6. nu-*-x86_64-linux-gnu-full.tar.gz 7. nu-*-x86_64-linux-musl-full.tar.gz 8. nu-*-x86_64-windows-msvc-full.msi 9. nu-*-x86_64-windows-msvc-full.zip
2023-09-23 01:41:08 +00:00
- name: Release Nu Binary
id: nu
run: nu .github/workflows/release-pkg.nu
env:
RELEASE_TYPE: standard
OS: ${{ matrix.os }}
REF: ${{ github.ref }}
TARGET: ${{ matrix.target }}
_EXTRA_: ${{ matrix.extra }}
TARGET_RUSTFLAGS: ${{ matrix.target_rustflags }}
# REF: https://github.com/marketplace/actions/gh-release
- name: Publish Archive
Bump softprops/action-gh-release from 2.0.1 to 2.0.4 (#12191)
2024-03-13 01:23:24 +00:00
uses: softprops/action-gh-release@v2.0.4
Add full releases of Nu binaries along with the standard releases (#10457) # Description Add full releases of Nu binaries along with the standard releases, close: https://github.com/nushell/nushell/issues/10322 A full release means: 1. Build with `--features=dataframe,extra` flag 2. Contains `-full` in the package name ### **A test release could be found in the nushell/nightly Repo: https://github.com/nushell/nightly/releases/tag/v0.85.1** The action running log: https://github.com/nushell/nightly/actions/runs/6260611553 # User-Facing Changes Will attach the following release packages along with the official ones as before: 1. nu-*-aarch64-darwin-full.tar.gz 2. nu-*-aarch64-linux-gnu-full.tar.gz 3. nu-*-aarch64-windows-msvc-full.msi 4. nu-*-aarch64-windows-msvc-full.zip 5. nu-*-x86_64-darwin-full.tar.gz 6. nu-*-x86_64-linux-gnu-full.tar.gz 7. nu-*-x86_64-linux-musl-full.tar.gz 8. nu-*-x86_64-windows-msvc-full.msi 9. nu-*-x86_64-windows-msvc-full.zip
2023-09-23 01:41:08 +00:00
if: ${{ startsWith(github.ref, 'refs/tags/') }}
Prevent `rustflags` build config from being ignored in ci workflows (#9513) # Description Prevent `rustflags` build configuration from being ignored in github actions ci workflows. [actions-rust-lang/setup-rust-toolchain](https://github.com/actions-rust-lang/setup-rust-toolchain/) used in ci workflows sets `RUSTFLAGS="-D warnings"` env variable by default. It has priority over some other sources of `rustflags` as described in [the cargo reference](https://doc.rust-lang.org/cargo/reference/config.html#buildrustflags). Nushell is using `target.x86_64-pc-windows-msvc.rustflags` to statically link MSVC runtime in windows platform, but this config is being ignored in ci workflows. By unsetting `RUSTFLAGS` env variable, `rustflags` build configurations will be properly used in ci workflows. I assume that this was the cause of the installer verification failures on the recent winget submission PRs. For more details, refer discussions in https://github.com/microsoft/winget-pkgs/pull/106977 and https://github.com/nushell/nushell/pull/9322#issuecomment-1602932971. # User-Facing Changes Pre-built releases for windows that are created by the release ci workflow will now contain statically linked MSVC runtime. # Tests + Formatting Confirmed successful installation in a windows sandbox instance, which was failing before. It also contains changes made in #9514. Release ci workflow: https://github.com/wolimst/nushell/actions/runs/5357440849 Installer: https://github.com/wolimst/nushell/releases/tag/0.81.0-test # After Submitting Need to check the installer verification result in a winget submission PR for the next release, if this PR gets merged.
2023-06-23 19:53:45 +00:00
with:
Improve release script for github release workflow (#10502) # Description Improve release script for Github release workflow: Just some small improvements
2023-09-25 11:55:51 +00:00
draft: true
Add full releases of Nu binaries along with the standard releases (#10457) # Description Add full releases of Nu binaries along with the standard releases, close: https://github.com/nushell/nushell/issues/10322 A full release means: 1. Build with `--features=dataframe,extra` flag 2. Contains `-full` in the package name ### **A test release could be found in the nushell/nightly Repo: https://github.com/nushell/nightly/releases/tag/v0.85.1** The action running log: https://github.com/nushell/nightly/actions/runs/6260611553 # User-Facing Changes Will attach the following release packages along with the official ones as before: 1. nu-*-aarch64-darwin-full.tar.gz 2. nu-*-aarch64-linux-gnu-full.tar.gz 3. nu-*-aarch64-windows-msvc-full.msi 4. nu-*-aarch64-windows-msvc-full.zip 5. nu-*-x86_64-darwin-full.tar.gz 6. nu-*-x86_64-linux-gnu-full.tar.gz 7. nu-*-x86_64-linux-musl-full.tar.gz 8. nu-*-x86_64-windows-msvc-full.msi 9. nu-*-x86_64-windows-msvc-full.zip
2023-09-23 01:41:08 +00:00
files: ${{ steps.nu.outputs.archive }}
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
full:
name: Full
strategy:
fail-fast: false
matrix:
target:
- aarch64-apple-darwin
- x86_64-apple-darwin
- x86_64-pc-windows-msvc
- aarch64-pc-windows-msvc
- x86_64-unknown-linux-gnu
- x86_64-unknown-linux-musl
- aarch64-unknown-linux-gnu
extra: ['bin']
include:
- target: aarch64-apple-darwin
os: macos-latest
Remove feat `extra` and include in default (#12140) # Description The intended effect of the `extra` feature has been undermined by introducing the full builds on our release pages and having more activity on some of the extra commands. To simplify the feature matrix let's get rid of it and focus our effort on truly either refining a command to well-specified behavior or discarding it entirely from the `nu` binary and moving it into plugins. ## Details - Remove `--features extra` from CI - Don't explicitly name `extra` in full build wf - Remove feature extra from build-help scripts - Update README in `nu-cmd-extra` - Remove feature `extra` - Fix previously dead `format pattern` tests - Relax signature of `to html` - Fix/ignore `html::test_no_color_flag` - Remove dead features from `version` - Refine `to html` type signature # User-Facing Changes The commands that were previously only available when building with `--features extra` will now be available to everyone. This increases the number of dependencies slightly but has a limited impact on the overall binary size. # Tests + Formatting Some tests that were left in `nu-command` during cratification were dead because the feature was not passed to `nu-command` and only to `nu-cmd-lang` for feature-flag mention in `version`. Those tests have now been either fixed or ignored in one case. # After Submitting There may be places in the documentation where we point to `--features extra` that will now be moot (apart from the generated command help)
2024-03-10 16:29:02 +00:00
target_rustflags: '--features=dataframe'
Add full releases of Nu binaries along with the standard releases (#10457) # Description Add full releases of Nu binaries along with the standard releases, close: https://github.com/nushell/nushell/issues/10322 A full release means: 1. Build with `--features=dataframe,extra` flag 2. Contains `-full` in the package name ### **A test release could be found in the nushell/nightly Repo: https://github.com/nushell/nightly/releases/tag/v0.85.1** The action running log: https://github.com/nushell/nightly/actions/runs/6260611553 # User-Facing Changes Will attach the following release packages along with the official ones as before: 1. nu-*-aarch64-darwin-full.tar.gz 2. nu-*-aarch64-linux-gnu-full.tar.gz 3. nu-*-aarch64-windows-msvc-full.msi 4. nu-*-aarch64-windows-msvc-full.zip 5. nu-*-x86_64-darwin-full.tar.gz 6. nu-*-x86_64-linux-gnu-full.tar.gz 7. nu-*-x86_64-linux-musl-full.tar.gz 8. nu-*-x86_64-windows-msvc-full.msi 9. nu-*-x86_64-windows-msvc-full.zip
2023-09-23 01:41:08 +00:00
- target: x86_64-apple-darwin
os: macos-latest
Remove feat `extra` and include in default (#12140) # Description The intended effect of the `extra` feature has been undermined by introducing the full builds on our release pages and having more activity on some of the extra commands. To simplify the feature matrix let's get rid of it and focus our effort on truly either refining a command to well-specified behavior or discarding it entirely from the `nu` binary and moving it into plugins. ## Details - Remove `--features extra` from CI - Don't explicitly name `extra` in full build wf - Remove feature extra from build-help scripts - Update README in `nu-cmd-extra` - Remove feature `extra` - Fix previously dead `format pattern` tests - Relax signature of `to html` - Fix/ignore `html::test_no_color_flag` - Remove dead features from `version` - Refine `to html` type signature # User-Facing Changes The commands that were previously only available when building with `--features extra` will now be available to everyone. This increases the number of dependencies slightly but has a limited impact on the overall binary size. # Tests + Formatting Some tests that were left in `nu-command` during cratification were dead because the feature was not passed to `nu-command` and only to `nu-cmd-lang` for feature-flag mention in `version`. Those tests have now been either fixed or ignored in one case. # After Submitting There may be places in the documentation where we point to `--features extra` that will now be moot (apart from the generated command help)
2024-03-10 16:29:02 +00:00
target_rustflags: '--features=dataframe'
Add full releases of Nu binaries along with the standard releases (#10457) # Description Add full releases of Nu binaries along with the standard releases, close: https://github.com/nushell/nushell/issues/10322 A full release means: 1. Build with `--features=dataframe,extra` flag 2. Contains `-full` in the package name ### **A test release could be found in the nushell/nightly Repo: https://github.com/nushell/nightly/releases/tag/v0.85.1** The action running log: https://github.com/nushell/nightly/actions/runs/6260611553 # User-Facing Changes Will attach the following release packages along with the official ones as before: 1. nu-*-aarch64-darwin-full.tar.gz 2. nu-*-aarch64-linux-gnu-full.tar.gz 3. nu-*-aarch64-windows-msvc-full.msi 4. nu-*-aarch64-windows-msvc-full.zip 5. nu-*-x86_64-darwin-full.tar.gz 6. nu-*-x86_64-linux-gnu-full.tar.gz 7. nu-*-x86_64-linux-musl-full.tar.gz 8. nu-*-x86_64-windows-msvc-full.msi 9. nu-*-x86_64-windows-msvc-full.zip
2023-09-23 01:41:08 +00:00
- target: x86_64-pc-windows-msvc
extra: 'bin'
os: windows-latest
Remove feat `extra` and include in default (#12140) # Description The intended effect of the `extra` feature has been undermined by introducing the full builds on our release pages and having more activity on some of the extra commands. To simplify the feature matrix let's get rid of it and focus our effort on truly either refining a command to well-specified behavior or discarding it entirely from the `nu` binary and moving it into plugins. ## Details - Remove `--features extra` from CI - Don't explicitly name `extra` in full build wf - Remove feature extra from build-help scripts - Update README in `nu-cmd-extra` - Remove feature `extra` - Fix previously dead `format pattern` tests - Relax signature of `to html` - Fix/ignore `html::test_no_color_flag` - Remove dead features from `version` - Refine `to html` type signature # User-Facing Changes The commands that were previously only available when building with `--features extra` will now be available to everyone. This increases the number of dependencies slightly but has a limited impact on the overall binary size. # Tests + Formatting Some tests that were left in `nu-command` during cratification were dead because the feature was not passed to `nu-command` and only to `nu-cmd-lang` for feature-flag mention in `version`. Those tests have now been either fixed or ignored in one case. # After Submitting There may be places in the documentation where we point to `--features extra` that will now be moot (apart from the generated command help)
2024-03-10 16:29:02 +00:00
target_rustflags: '--features=dataframe'
Add full releases of Nu binaries along with the standard releases (#10457) # Description Add full releases of Nu binaries along with the standard releases, close: https://github.com/nushell/nushell/issues/10322 A full release means: 1. Build with `--features=dataframe,extra` flag 2. Contains `-full` in the package name ### **A test release could be found in the nushell/nightly Repo: https://github.com/nushell/nightly/releases/tag/v0.85.1** The action running log: https://github.com/nushell/nightly/actions/runs/6260611553 # User-Facing Changes Will attach the following release packages along with the official ones as before: 1. nu-*-aarch64-darwin-full.tar.gz 2. nu-*-aarch64-linux-gnu-full.tar.gz 3. nu-*-aarch64-windows-msvc-full.msi 4. nu-*-aarch64-windows-msvc-full.zip 5. nu-*-x86_64-darwin-full.tar.gz 6. nu-*-x86_64-linux-gnu-full.tar.gz 7. nu-*-x86_64-linux-musl-full.tar.gz 8. nu-*-x86_64-windows-msvc-full.msi 9. nu-*-x86_64-windows-msvc-full.zip
2023-09-23 01:41:08 +00:00
- target: x86_64-pc-windows-msvc
extra: msi
os: windows-latest
Remove feat `extra` and include in default (#12140) # Description The intended effect of the `extra` feature has been undermined by introducing the full builds on our release pages and having more activity on some of the extra commands. To simplify the feature matrix let's get rid of it and focus our effort on truly either refining a command to well-specified behavior or discarding it entirely from the `nu` binary and moving it into plugins. ## Details - Remove `--features extra` from CI - Don't explicitly name `extra` in full build wf - Remove feature extra from build-help scripts - Update README in `nu-cmd-extra` - Remove feature `extra` - Fix previously dead `format pattern` tests - Relax signature of `to html` - Fix/ignore `html::test_no_color_flag` - Remove dead features from `version` - Refine `to html` type signature # User-Facing Changes The commands that were previously only available when building with `--features extra` will now be available to everyone. This increases the number of dependencies slightly but has a limited impact on the overall binary size. # Tests + Formatting Some tests that were left in `nu-command` during cratification were dead because the feature was not passed to `nu-command` and only to `nu-cmd-lang` for feature-flag mention in `version`. Those tests have now been either fixed or ignored in one case. # After Submitting There may be places in the documentation where we point to `--features extra` that will now be moot (apart from the generated command help)
2024-03-10 16:29:02 +00:00
target_rustflags: '--features=dataframe'
Add full releases of Nu binaries along with the standard releases (#10457) # Description Add full releases of Nu binaries along with the standard releases, close: https://github.com/nushell/nushell/issues/10322 A full release means: 1. Build with `--features=dataframe,extra` flag 2. Contains `-full` in the package name ### **A test release could be found in the nushell/nightly Repo: https://github.com/nushell/nightly/releases/tag/v0.85.1** The action running log: https://github.com/nushell/nightly/actions/runs/6260611553 # User-Facing Changes Will attach the following release packages along with the official ones as before: 1. nu-*-aarch64-darwin-full.tar.gz 2. nu-*-aarch64-linux-gnu-full.tar.gz 3. nu-*-aarch64-windows-msvc-full.msi 4. nu-*-aarch64-windows-msvc-full.zip 5. nu-*-x86_64-darwin-full.tar.gz 6. nu-*-x86_64-linux-gnu-full.tar.gz 7. nu-*-x86_64-linux-musl-full.tar.gz 8. nu-*-x86_64-windows-msvc-full.msi 9. nu-*-x86_64-windows-msvc-full.zip
2023-09-23 01:41:08 +00:00
- target: aarch64-pc-windows-msvc
extra: 'bin'
os: windows-latest
Remove feat `extra` and include in default (#12140) # Description The intended effect of the `extra` feature has been undermined by introducing the full builds on our release pages and having more activity on some of the extra commands. To simplify the feature matrix let's get rid of it and focus our effort on truly either refining a command to well-specified behavior or discarding it entirely from the `nu` binary and moving it into plugins. ## Details - Remove `--features extra` from CI - Don't explicitly name `extra` in full build wf - Remove feature extra from build-help scripts - Update README in `nu-cmd-extra` - Remove feature `extra` - Fix previously dead `format pattern` tests - Relax signature of `to html` - Fix/ignore `html::test_no_color_flag` - Remove dead features from `version` - Refine `to html` type signature # User-Facing Changes The commands that were previously only available when building with `--features extra` will now be available to everyone. This increases the number of dependencies slightly but has a limited impact on the overall binary size. # Tests + Formatting Some tests that were left in `nu-command` during cratification were dead because the feature was not passed to `nu-command` and only to `nu-cmd-lang` for feature-flag mention in `version`. Those tests have now been either fixed or ignored in one case. # After Submitting There may be places in the documentation where we point to `--features extra` that will now be moot (apart from the generated command help)
2024-03-10 16:29:02 +00:00
target_rustflags: '--features=dataframe'
Add full releases of Nu binaries along with the standard releases (#10457) # Description Add full releases of Nu binaries along with the standard releases, close: https://github.com/nushell/nushell/issues/10322 A full release means: 1. Build with `--features=dataframe,extra` flag 2. Contains `-full` in the package name ### **A test release could be found in the nushell/nightly Repo: https://github.com/nushell/nightly/releases/tag/v0.85.1** The action running log: https://github.com/nushell/nightly/actions/runs/6260611553 # User-Facing Changes Will attach the following release packages along with the official ones as before: 1. nu-*-aarch64-darwin-full.tar.gz 2. nu-*-aarch64-linux-gnu-full.tar.gz 3. nu-*-aarch64-windows-msvc-full.msi 4. nu-*-aarch64-windows-msvc-full.zip 5. nu-*-x86_64-darwin-full.tar.gz 6. nu-*-x86_64-linux-gnu-full.tar.gz 7. nu-*-x86_64-linux-musl-full.tar.gz 8. nu-*-x86_64-windows-msvc-full.msi 9. nu-*-x86_64-windows-msvc-full.zip
2023-09-23 01:41:08 +00:00
- target: aarch64-pc-windows-msvc
extra: msi
os: windows-latest
Remove feat `extra` and include in default (#12140) # Description The intended effect of the `extra` feature has been undermined by introducing the full builds on our release pages and having more activity on some of the extra commands. To simplify the feature matrix let's get rid of it and focus our effort on truly either refining a command to well-specified behavior or discarding it entirely from the `nu` binary and moving it into plugins. ## Details - Remove `--features extra` from CI - Don't explicitly name `extra` in full build wf - Remove feature extra from build-help scripts - Update README in `nu-cmd-extra` - Remove feature `extra` - Fix previously dead `format pattern` tests - Relax signature of `to html` - Fix/ignore `html::test_no_color_flag` - Remove dead features from `version` - Refine `to html` type signature # User-Facing Changes The commands that were previously only available when building with `--features extra` will now be available to everyone. This increases the number of dependencies slightly but has a limited impact on the overall binary size. # Tests + Formatting Some tests that were left in `nu-command` during cratification were dead because the feature was not passed to `nu-command` and only to `nu-cmd-lang` for feature-flag mention in `version`. Those tests have now been either fixed or ignored in one case. # After Submitting There may be places in the documentation where we point to `--features extra` that will now be moot (apart from the generated command help)
2024-03-10 16:29:02 +00:00
target_rustflags: '--features=dataframe'
Add full releases of Nu binaries along with the standard releases (#10457) # Description Add full releases of Nu binaries along with the standard releases, close: https://github.com/nushell/nushell/issues/10322 A full release means: 1. Build with `--features=dataframe,extra` flag 2. Contains `-full` in the package name ### **A test release could be found in the nushell/nightly Repo: https://github.com/nushell/nightly/releases/tag/v0.85.1** The action running log: https://github.com/nushell/nightly/actions/runs/6260611553 # User-Facing Changes Will attach the following release packages along with the official ones as before: 1. nu-*-aarch64-darwin-full.tar.gz 2. nu-*-aarch64-linux-gnu-full.tar.gz 3. nu-*-aarch64-windows-msvc-full.msi 4. nu-*-aarch64-windows-msvc-full.zip 5. nu-*-x86_64-darwin-full.tar.gz 6. nu-*-x86_64-linux-gnu-full.tar.gz 7. nu-*-x86_64-linux-musl-full.tar.gz 8. nu-*-x86_64-windows-msvc-full.msi 9. nu-*-x86_64-windows-msvc-full.zip
2023-09-23 01:41:08 +00:00
- target: x86_64-unknown-linux-gnu
os: ubuntu-20.04
Remove feat `extra` and include in default (#12140) # Description The intended effect of the `extra` feature has been undermined by introducing the full builds on our release pages and having more activity on some of the extra commands. To simplify the feature matrix let's get rid of it and focus our effort on truly either refining a command to well-specified behavior or discarding it entirely from the `nu` binary and moving it into plugins. ## Details - Remove `--features extra` from CI - Don't explicitly name `extra` in full build wf - Remove feature extra from build-help scripts - Update README in `nu-cmd-extra` - Remove feature `extra` - Fix previously dead `format pattern` tests - Relax signature of `to html` - Fix/ignore `html::test_no_color_flag` - Remove dead features from `version` - Refine `to html` type signature # User-Facing Changes The commands that were previously only available when building with `--features extra` will now be available to everyone. This increases the number of dependencies slightly but has a limited impact on the overall binary size. # Tests + Formatting Some tests that were left in `nu-command` during cratification were dead because the feature was not passed to `nu-command` and only to `nu-cmd-lang` for feature-flag mention in `version`. Those tests have now been either fixed or ignored in one case. # After Submitting There may be places in the documentation where we point to `--features extra` that will now be moot (apart from the generated command help)
2024-03-10 16:29:02 +00:00
target_rustflags: '--features=dataframe'
Add full releases of Nu binaries along with the standard releases (#10457) # Description Add full releases of Nu binaries along with the standard releases, close: https://github.com/nushell/nushell/issues/10322 A full release means: 1. Build with `--features=dataframe,extra` flag 2. Contains `-full` in the package name ### **A test release could be found in the nushell/nightly Repo: https://github.com/nushell/nightly/releases/tag/v0.85.1** The action running log: https://github.com/nushell/nightly/actions/runs/6260611553 # User-Facing Changes Will attach the following release packages along with the official ones as before: 1. nu-*-aarch64-darwin-full.tar.gz 2. nu-*-aarch64-linux-gnu-full.tar.gz 3. nu-*-aarch64-windows-msvc-full.msi 4. nu-*-aarch64-windows-msvc-full.zip 5. nu-*-x86_64-darwin-full.tar.gz 6. nu-*-x86_64-linux-gnu-full.tar.gz 7. nu-*-x86_64-linux-musl-full.tar.gz 8. nu-*-x86_64-windows-msvc-full.msi 9. nu-*-x86_64-windows-msvc-full.zip
2023-09-23 01:41:08 +00:00
- target: x86_64-unknown-linux-musl
os: ubuntu-20.04
Remove feat `extra` and include in default (#12140) # Description The intended effect of the `extra` feature has been undermined by introducing the full builds on our release pages and having more activity on some of the extra commands. To simplify the feature matrix let's get rid of it and focus our effort on truly either refining a command to well-specified behavior or discarding it entirely from the `nu` binary and moving it into plugins. ## Details - Remove `--features extra` from CI - Don't explicitly name `extra` in full build wf - Remove feature extra from build-help scripts - Update README in `nu-cmd-extra` - Remove feature `extra` - Fix previously dead `format pattern` tests - Relax signature of `to html` - Fix/ignore `html::test_no_color_flag` - Remove dead features from `version` - Refine `to html` type signature # User-Facing Changes The commands that were previously only available when building with `--features extra` will now be available to everyone. This increases the number of dependencies slightly but has a limited impact on the overall binary size. # Tests + Formatting Some tests that were left in `nu-command` during cratification were dead because the feature was not passed to `nu-command` and only to `nu-cmd-lang` for feature-flag mention in `version`. Those tests have now been either fixed or ignored in one case. # After Submitting There may be places in the documentation where we point to `--features extra` that will now be moot (apart from the generated command help)
2024-03-10 16:29:02 +00:00
target_rustflags: '--features=dataframe'
Add full releases of Nu binaries along with the standard releases (#10457) # Description Add full releases of Nu binaries along with the standard releases, close: https://github.com/nushell/nushell/issues/10322 A full release means: 1. Build with `--features=dataframe,extra` flag 2. Contains `-full` in the package name ### **A test release could be found in the nushell/nightly Repo: https://github.com/nushell/nightly/releases/tag/v0.85.1** The action running log: https://github.com/nushell/nightly/actions/runs/6260611553 # User-Facing Changes Will attach the following release packages along with the official ones as before: 1. nu-*-aarch64-darwin-full.tar.gz 2. nu-*-aarch64-linux-gnu-full.tar.gz 3. nu-*-aarch64-windows-msvc-full.msi 4. nu-*-aarch64-windows-msvc-full.zip 5. nu-*-x86_64-darwin-full.tar.gz 6. nu-*-x86_64-linux-gnu-full.tar.gz 7. nu-*-x86_64-linux-musl-full.tar.gz 8. nu-*-x86_64-windows-msvc-full.msi 9. nu-*-x86_64-windows-msvc-full.zip
2023-09-23 01:41:08 +00:00
- target: aarch64-unknown-linux-gnu
os: ubuntu-20.04
Remove feat `extra` and include in default (#12140) # Description The intended effect of the `extra` feature has been undermined by introducing the full builds on our release pages and having more activity on some of the extra commands. To simplify the feature matrix let's get rid of it and focus our effort on truly either refining a command to well-specified behavior or discarding it entirely from the `nu` binary and moving it into plugins. ## Details - Remove `--features extra` from CI - Don't explicitly name `extra` in full build wf - Remove feature extra from build-help scripts - Update README in `nu-cmd-extra` - Remove feature `extra` - Fix previously dead `format pattern` tests - Relax signature of `to html` - Fix/ignore `html::test_no_color_flag` - Remove dead features from `version` - Refine `to html` type signature # User-Facing Changes The commands that were previously only available when building with `--features extra` will now be available to everyone. This increases the number of dependencies slightly but has a limited impact on the overall binary size. # Tests + Formatting Some tests that were left in `nu-command` during cratification were dead because the feature was not passed to `nu-command` and only to `nu-cmd-lang` for feature-flag mention in `version`. Those tests have now been either fixed or ignored in one case. # After Submitting There may be places in the documentation where we point to `--features extra` that will now be moot (apart from the generated command help)
2024-03-10 16:29:02 +00:00
target_rustflags: '--features=dataframe'
Add full releases of Nu binaries along with the standard releases (#10457) # Description Add full releases of Nu binaries along with the standard releases, close: https://github.com/nushell/nushell/issues/10322 A full release means: 1. Build with `--features=dataframe,extra` flag 2. Contains `-full` in the package name ### **A test release could be found in the nushell/nightly Repo: https://github.com/nushell/nightly/releases/tag/v0.85.1** The action running log: https://github.com/nushell/nightly/actions/runs/6260611553 # User-Facing Changes Will attach the following release packages along with the official ones as before: 1. nu-*-aarch64-darwin-full.tar.gz 2. nu-*-aarch64-linux-gnu-full.tar.gz 3. nu-*-aarch64-windows-msvc-full.msi 4. nu-*-aarch64-windows-msvc-full.zip 5. nu-*-x86_64-darwin-full.tar.gz 6. nu-*-x86_64-linux-gnu-full.tar.gz 7. nu-*-x86_64-linux-musl-full.tar.gz 8. nu-*-x86_64-windows-msvc-full.msi 9. nu-*-x86_64-windows-msvc-full.zip
2023-09-23 01:41:08 +00:00
runs-on: ${{matrix.os}}
steps:
Bump actions/checkout from 4.1.4 to 4.1.5 (#12804) Bumps [actions/checkout](https://github.com/actions/checkout) from 4.1.4 to 4.1.5. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/actions/checkout/releases">actions/checkout's releases</a>.</em></p> <blockquote> <h2>v4.1.5</h2> <h2>What's Changed</h2> <ul> <li>Update NPM dependencies by <a href="https://github.com/cory-miller"><code>@​cory-miller</code></a> in <a href="https://redirect.github.com/actions/checkout/pull/1703">actions/checkout#1703</a></li> <li>Bump github/codeql-action from 2 to 3 by <a href="https://github.com/dependabot"><code>@​dependabot</code></a> in <a href="https://redirect.github.com/actions/checkout/pull/1694">actions/checkout#1694</a></li> <li>Bump actions/setup-node from 1 to 4 by <a href="https://github.com/dependabot"><code>@​dependabot</code></a> in <a href="https://redirect.github.com/actions/checkout/pull/1696">actions/checkout#1696</a></li> <li>Bump actions/upload-artifact from 2 to 4 by <a href="https://github.com/dependabot"><code>@​dependabot</code></a> in <a href="https://redirect.github.com/actions/checkout/pull/1695">actions/checkout#1695</a></li> <li>README: Suggest <code>user.email</code> to be <code>41898282+github-actions[bot]@users.noreply.github.com</code> by <a href="https://github.com/cory-miller"><code>@​cory-miller</code></a> in <a href="https://redirect.github.com/actions/checkout/pull/1707">actions/checkout#1707</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/actions/checkout/compare/v4.1.4...v4.1.5">https://github.com/actions/checkout/compare/v4.1.4...v4.1.5</a></p> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/actions/checkout/blob/main/CHANGELOG.md">actions/checkout's changelog</a>.</em></p> <blockquote> <h1>Changelog</h1> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/actions/checkout/commit/44c2b7a8a4ea60a981eaca3cf939b5f4305c123b"><code>44c2b7a</code></a> README: Suggest <code>user.email</code> to be `41898282+github-actions[bot]<a href="https://github.com/users"><code>@​users</code></a>.norepl...</li> <li><a href="https://github.com/actions/checkout/commit/8459bc0c7e3759cdf591f513d9f141a95fef0a8f"><code>8459bc0</code></a> Bump actions/upload-artifact from 2 to 4 (<a href="https://redirect.github.com/actions/checkout/issues/1695">#1695</a>)</li> <li><a href="https://github.com/actions/checkout/commit/3f603f6d5e9f40714f97b2f017aa0df2a443192a"><code>3f603f6</code></a> Bump actions/setup-node from 1 to 4 (<a href="https://redirect.github.com/actions/checkout/issues/1696">#1696</a>)</li> <li><a href="https://github.com/actions/checkout/commit/fd084cde189b7b76ec305d52e27be545a0172823"><code>fd084cd</code></a> Bump github/codeql-action from 2 to 3 (<a href="https://redirect.github.com/actions/checkout/issues/1694">#1694</a>)</li> <li><a href="https://github.com/actions/checkout/commit/9c1e94e0ad997d618b6113a2171b055037589028"><code>9c1e94e</code></a> Update NPM dependencies (<a href="https://redirect.github.com/actions/checkout/issues/1703">#1703</a>)</li> <li>See full diff in <a href="https://github.com/actions/checkout/compare/v4.1.4...v4.1.5">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=actions/checkout&package-manager=github_actions&previous-version=4.1.4&new-version=4.1.5)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> 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) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2024-05-08 02:35:08 +00:00
- uses: actions/checkout@v4.1.5
Add full releases of Nu binaries along with the standard releases (#10457) # Description Add full releases of Nu binaries along with the standard releases, close: https://github.com/nushell/nushell/issues/10322 A full release means: 1. Build with `--features=dataframe,extra` flag 2. Contains `-full` in the package name ### **A test release could be found in the nushell/nightly Repo: https://github.com/nushell/nightly/releases/tag/v0.85.1** The action running log: https://github.com/nushell/nightly/actions/runs/6260611553 # User-Facing Changes Will attach the following release packages along with the official ones as before: 1. nu-*-aarch64-darwin-full.tar.gz 2. nu-*-aarch64-linux-gnu-full.tar.gz 3. nu-*-aarch64-windows-msvc-full.msi 4. nu-*-aarch64-windows-msvc-full.zip 5. nu-*-x86_64-darwin-full.tar.gz 6. nu-*-x86_64-linux-gnu-full.tar.gz 7. nu-*-x86_64-linux-musl-full.tar.gz 8. nu-*-x86_64-windows-msvc-full.msi 9. nu-*-x86_64-windows-msvc-full.zip
2023-09-23 01:41:08 +00:00
- name: Update Rust Toolchain Target
run: |
echo "targets = ['${{matrix.target}}']" >> rust-toolchain.toml
Tweak release workflow after `0.92.1` lessons (#12401) Encountered repeated build failure that vanished after clearing the existing build caches. - Don't `fail-fast` (this is highly annoying, if a severe problem is detected, there is still the possibility to intervene manually) - Don't cache the build process, we do it rarely so any potential speed-up is offset by the uncertainty if this affects the artefact
2024-04-06 02:20:01 +00:00
- name: Setup Rust toolchain
Bump actions-rust-lang/setup-rust-toolchain from 1.6.0 to 1.8.0 (#11539) Bumps [actions-rust-lang/setup-rust-toolchain](https://github.com/actions-rust-lang/setup-rust-toolchain) from 1.6.0 to 1.8.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/actions-rust-lang/setup-rust-toolchain/releases">actions-rust-lang/setup-rust-toolchain's releases</a>.</em></p> <blockquote> <h2>v1.8.0</h2> <ul> <li>Allow specifying subdirectories for cache.</li> <li>Fix toolchain file overriding.</li> </ul> <h2>v1.7.0</h2> <h2>What's Changed</h2> <ul> <li>Allow overriding the toolchain file by <a href="https://github.com/Twey"><code>@​Twey</code></a> in <a href="https://redirect.github.com/actions-rust-lang/setup-rust-toolchain/pull/26">actions-rust-lang/setup-rust-toolchain#26</a></li> <li>ci: update checked rust-toolchain version by <a href="https://github.com/robjtede"><code>@​robjtede</code></a> in <a href="https://redirect.github.com/actions-rust-lang/setup-rust-toolchain/pull/29">actions-rust-lang/setup-rust-toolchain#29</a></li> <li>Prepare 1.7.0 release by <a href="https://github.com/robjtede"><code>@​robjtede</code></a> in <a href="https://redirect.github.com/actions-rust-lang/setup-rust-toolchain/pull/30">actions-rust-lang/setup-rust-toolchain#30</a></li> </ul> <h2>New Contributors</h2> <ul> <li><a href="https://github.com/Twey"><code>@​Twey</code></a> made their first contribution in <a href="https://redirect.github.com/actions-rust-lang/setup-rust-toolchain/pull/26">actions-rust-lang/setup-rust-toolchain#26</a></li> <li><a href="https://github.com/robjtede"><code>@​robjtede</code></a> made their first contribution in <a href="https://redirect.github.com/actions-rust-lang/setup-rust-toolchain/pull/29">actions-rust-lang/setup-rust-toolchain#29</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/actions-rust-lang/setup-rust-toolchain/compare/v1.6...v1.7.0">https://github.com/actions-rust-lang/setup-rust-toolchain/compare/v1.6...v1.7.0</a></p> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/actions-rust-lang/setup-rust-toolchain/blob/main/CHANGELOG.md">actions-rust-lang/setup-rust-toolchain's changelog</a>.</em></p> <blockquote> <h2>[1.8.0] - 2024-01-13</h2> <ul> <li>Allow specifying subdirectories for cache.</li> <li>Fix toolchain file overriding.</li> </ul> <h2>[1.7.0] - 2024-01-11</h2> <ul> <li>Allow overriding the toolchain file with explicit <code>toolchain</code> input. (<a href="https://redirect.github.com/actions-rust-lang/setup-rust-toolchain/issues/26">#26</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/actions-rust-lang/setup-rust-toolchain/commit/b113a30d27a8e59c969077c0a0168cc13dab5ffc"><code>b113a30</code></a> Merge pull request <a href="https://redirect.github.com/actions-rust-lang/setup-rust-toolchain/issues/34">#34</a> from actions-rust-lang/rel-180</li> <li><a href="https://github.com/actions-rust-lang/setup-rust-toolchain/commit/039765bd186526e4d2e1b2f3ec14f5216b4d92bc"><code>039765b</code></a> chore: prepare release 1.8.0</li> <li><a href="https://github.com/actions-rust-lang/setup-rust-toolchain/commit/84e65ce3155f72bc64fcd3fbc1eab7814e937925"><code>84e65ce</code></a> Merge pull request <a href="https://redirect.github.com/actions-rust-lang/setup-rust-toolchain/issues/32">#32</a> from gruebel/add-workspaces</li> <li><a href="https://github.com/actions-rust-lang/setup-rust-toolchain/commit/6f719a240eaaea9ba9c138657ae60ae23314e892"><code>6f719a2</code></a> Merge branch 'main' into add-workspaces</li> <li><a href="https://github.com/actions-rust-lang/setup-rust-toolchain/commit/15d0afaad9a057d55c8c95034bfb3aacb990a6b0"><code>15d0afa</code></a> ci: fix cache test</li> <li><a href="https://github.com/actions-rust-lang/setup-rust-toolchain/commit/922cc935eba0313aadf10debf4b777609f674024"><code>922cc93</code></a> ci: add cache-workspaces test</li> <li><a href="https://github.com/actions-rust-lang/setup-rust-toolchain/commit/bcda41b18de1f885ca4a1ccfc0cd120c57bfe9ca"><code>bcda41b</code></a> Merge pull request <a href="https://redirect.github.com/actions-rust-lang/setup-rust-toolchain/issues/33">#33</a> from fprasx/fprasx/fix-toolchain-overrides</li> <li><a href="https://github.com/actions-rust-lang/setup-rust-toolchain/commit/ba41ca6f71dca3d3a627600631fedb7f260d083e"><code>ba41ca6</code></a> ci: clearer test names</li> <li><a href="https://github.com/actions-rust-lang/setup-rust-toolchain/commit/aa089182f268c0255577cdc57a82a9b0819d59c3"><code>aa08918</code></a> ci: fix conditional</li> <li><a href="https://github.com/actions-rust-lang/setup-rust-toolchain/commit/c6086ae6e539b9cca10fba3642fe77e559ba5705"><code>c6086ae</code></a> test: add toolchain file override test</li> <li>Additional commits viewable in <a href="https://github.com/actions-rust-lang/setup-rust-toolchain/compare/v1.6.0...v1.8.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=actions-rust-lang/setup-rust-toolchain&package-manager=github_actions&previous-version=1.6.0&new-version=1.8.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> 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) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2024-01-15 02:27:41 +00:00
uses: actions-rust-lang/setup-rust-toolchain@v1.8.0
Fix winget release submission error (#10757) <!-- if this PR closes one or more issues, you can automatically link the PR with them by using one of the [*linking keywords*](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword), e.g. - this PR should close #xxxx - fixes #xxxx you can also mention related issues, PRs or discussions! --> # Description <!-- Thank you for improving Nushell. Please, check our [contributing guide](../CONTRIBUTING.md) and talk to the core team before making major changes. Description of your pull request goes here. **Provide examples and/or screenshots** if your changes affect the user experience. --> Fix winget release submission error, more details could be found here: https://github.com/nushell/nushell/pull/5812#issuecomment-1768294811 @fdncred @wolimst # User-Facing Changes <!-- List of all changes that impact the user experience here. This helps us keep track of breaking changes. --> # Tests + Formatting <!-- Don't forget to add tests that cover your changes. Make sure you've run and fixed any issues with these commands: - `cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - `cargo clippy --workspace -- -D warnings -D clippy::unwrap_used` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass (on Windows make sure to [enable developer mode](https://learn.microsoft.com/en-us/windows/apps/get-started/developer-mode-features-and-debugging)) - `cargo run -- -c "use std testing; testing run-tests --path crates/nu-std"` to run the tests for the standard library > **Note** > from `nushell` you can also use the `toolkit` as follows > ```bash > use toolkit.nu # or use an `env_change` hook to activate it automatically > toolkit check pr > ``` --> # After Submitting <!-- If your PR had any user-facing changes, update [the documentation](https://github.com/nushell/nushell.github.io) after the PR is merged, if necessary. This will help us keep the docs up to date. --> --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-10-18 18:00:19 +00:00
# WARN: Keep the rustflags to prevent from the winget submission error: `CAQuietExec: Error 0xc0000135`
with:
Tweak release workflow after `0.92.1` lessons (#12401) Encountered repeated build failure that vanished after clearing the existing build caches. - Don't `fail-fast` (this is highly annoying, if a severe problem is detected, there is still the possibility to intervene manually) - Don't cache the build process, we do it rarely so any potential speed-up is offset by the uncertainty if this affects the artefact
2024-04-06 02:20:01 +00:00
cache: false
Fix winget release submission error (#10757) <!-- if this PR closes one or more issues, you can automatically link the PR with them by using one of the [*linking keywords*](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword), e.g. - this PR should close #xxxx - fixes #xxxx you can also mention related issues, PRs or discussions! --> # Description <!-- Thank you for improving Nushell. Please, check our [contributing guide](../CONTRIBUTING.md) and talk to the core team before making major changes. Description of your pull request goes here. **Provide examples and/or screenshots** if your changes affect the user experience. --> Fix winget release submission error, more details could be found here: https://github.com/nushell/nushell/pull/5812#issuecomment-1768294811 @fdncred @wolimst # User-Facing Changes <!-- List of all changes that impact the user experience here. This helps us keep track of breaking changes. --> # Tests + Formatting <!-- Don't forget to add tests that cover your changes. Make sure you've run and fixed any issues with these commands: - `cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - `cargo clippy --workspace -- -D warnings -D clippy::unwrap_used` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass (on Windows make sure to [enable developer mode](https://learn.microsoft.com/en-us/windows/apps/get-started/developer-mode-features-and-debugging)) - `cargo run -- -c "use std testing; testing run-tests --path crates/nu-std"` to run the tests for the standard library > **Note** > from `nushell` you can also use the `toolkit` as follows > ```bash > use toolkit.nu # or use an `env_change` hook to activate it automatically > toolkit check pr > ``` --> # After Submitting <!-- If your PR had any user-facing changes, update [the documentation](https://github.com/nushell/nushell.github.io) after the PR is merged, if necessary. This will help us keep the docs up to date. --> --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-10-18 18:00:19 +00:00
rustflags: ''
Remove inactive actions-rs/toolchain@v1.0.6 for release workflow (#7302) # Description Remove inactive actions-rs/toolchain@v1.0.6 for release workflow, https://github.com/actions-rs/toolchain is inactive for more than two years, and have lots of unfixed warnings: https://github.com/actions-rs/toolchain/issues?q=is%3Aissue+is%3Aopen+warning After this PR: Workflow running result: https://github.com/hustcer/nu-release/actions/runs/3590194180 Release Test: https://github.com/hustcer/nu-release/releases/tag/v0.72.7
2022-12-01 08:30:25 +00:00
feat: Refactor and optimize the github release workflow: deliver binary package for more targets (#5649)
2022-05-28 02:41:47 +00:00
- name: Setup Nushell
Upgrade hustcer/setup-nu to v3.10 to fix macOS arm64 build errors (#12681) Upgrade hustcer/setup-nu to [v3.10](https://github.com/hustcer/setup-nu/releases/tag/v3.10) to fix macOS arm64 build errors Release Testing: https://github.com/nushell/nightly/actions/runs/8856404620
2024-04-27 02:18:08 +00:00
uses: hustcer/setup-nu@v3.10
feat: Refactor and optimize the github release workflow: deliver binary package for more targets (#5649)
2022-05-28 02:41:47 +00:00
with:
Upgrade Nu to v0.93.0 for nightly and release workflow (#12721)
2024-05-02 03:11:53 +00:00
version: 0.93.0
feat: Refactor and optimize the github release workflow: deliver binary package for more targets (#5649)
2022-05-28 02:41:47 +00:00
- name: Release Nu Binary
id: nu
run: nu .github/workflows/release-pkg.nu
env:
Add full releases of Nu binaries along with the standard releases (#10457) # Description Add full releases of Nu binaries along with the standard releases, close: https://github.com/nushell/nushell/issues/10322 A full release means: 1. Build with `--features=dataframe,extra` flag 2. Contains `-full` in the package name ### **A test release could be found in the nushell/nightly Repo: https://github.com/nushell/nightly/releases/tag/v0.85.1** The action running log: https://github.com/nushell/nightly/actions/runs/6260611553 # User-Facing Changes Will attach the following release packages along with the official ones as before: 1. nu-*-aarch64-darwin-full.tar.gz 2. nu-*-aarch64-linux-gnu-full.tar.gz 3. nu-*-aarch64-windows-msvc-full.msi 4. nu-*-aarch64-windows-msvc-full.zip 5. nu-*-x86_64-darwin-full.tar.gz 6. nu-*-x86_64-linux-gnu-full.tar.gz 7. nu-*-x86_64-linux-musl-full.tar.gz 8. nu-*-x86_64-windows-msvc-full.msi 9. nu-*-x86_64-windows-msvc-full.zip
2023-09-23 01:41:08 +00:00
RELEASE_TYPE: full
feat: Refactor and optimize the github release workflow: deliver binary package for more targets (#5649)
2022-05-28 02:41:47 +00:00
OS: ${{ matrix.os }}
REF: ${{ github.ref }}
TARGET: ${{ matrix.target }}
_EXTRA_: ${{ matrix.extra }}
TARGET_RUSTFLAGS: ${{ matrix.target_rustflags }}
# REF: https://github.com/marketplace/actions/gh-release
- name: Publish Archive
Bump softprops/action-gh-release from 2.0.1 to 2.0.4 (#12191)
2024-03-13 01:23:24 +00:00
uses: softprops/action-gh-release@v2.0.4
feat: Refactor and optimize the github release workflow: deliver binary package for more targets (#5649)
2022-05-28 02:41:47 +00:00
if: ${{ startsWith(github.ref, 'refs/tags/') }}
with:
draft: true
files: ${{ steps.nu.outputs.archive }}
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
Reference in a new issue Copy permalink