build!: bump rust to 1.76 and add rust update script

[lklimek]

Issue being fixed or feature implemented

New Rust was released

What was done?

• bumped version to 1.76 in github actions, rust-toolchain.toml, Dockerfile, Cargo.toml files and README.md
• added script that makes such updates easy

How Has This Been Tested?

Run script locally + Github Actions

Breaking Changes

New Rust version 1.76 is required

Checklist:

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or updated relevant unit/integration/functional/e2e tests
• I have added "!" to the title and described breaking changes in the corresponding section if my code contains any
• I have made corresponding changes to the documentation if needed

For repository code-owners and collaborators only

• I have assigned this pull request to a milestone

[shumkov]

Isn't it's using toolchain file if not set?

[shumkov]

Why did you remove new lines? I see it more readable rather then on block of test

[lklimek]

That's what yq tool did that I use to replace version in yaml.

I can try to refactor to use multi-line sed if you wish.

[shumkov]

Oh, you dynamically update it...

[shumkov]

Maybe just read it from the toolchain file instead of hardcoding?

Suggestion from ChatGPT:

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
    - uses: actions/checkout@v2
      # Checkout your repository

    - name: Extract Rust toolchain version
      id: rust_toolchain
      run: |
        TOOLCHAIN_VERSION=$(grep channel rust-toolchain.toml | awk '{print $3}' | tr -d '"')
        echo "TOOLCHAIN_VERSION=$TOOLCHAIN_VERSION" >> $GITHUB_ENV
        echo "::set-output name=version::$TOOLCHAIN_VERSION"
      # This command reads the rust-toolchain.toml, extracts the version, and sets it as an environment variable and step output

    # Use the extracted version in subsequent steps
    - name: Use Rust toolchain
      uses: actions-rs/toolchain@v1
      with:
        toolchain: ${{ steps.rust_toolchain.outputs.version }}
        override: true

I would use $GITHUB_OUTPUT though

[shumkov]

Why we set it here?

[lklimek]

I don't understand the question.

The rust-version field is an optional key that tells cargo what version of the Rust language and compiler your package can be compiled with.

As we only test on 1.76, we only support this version onwards.

[shumkov]

Yeah, I've never seen such an option, and since it's a minimal value then it's all good.

[shumkov]

Is this by mistake?

[lklimek]

yes, good point, missed this.

Will remove.

[shumkov]

Maybe just read it from the toolchain file instead of hardcoding?

Suggestion from ChatGPT:

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
    - uses: actions/checkout@v2
      # Checkout your repository

    - name: Extract Rust toolchain version
      id: rust_toolchain
      run: |
        TOOLCHAIN_VERSION=$(grep channel rust-toolchain.toml | awk '{print $3}' | tr -d '"')
        echo "TOOLCHAIN_VERSION=$TOOLCHAIN_VERSION" >> $GITHUB_ENV
        echo "::set-output name=version::$TOOLCHAIN_VERSION"
      # This command reads the rust-toolchain.toml, extracts the version, and sets it as an environment variable and step output

    # Use the extracted version in subsequent steps
    - name: Use Rust toolchain
      uses: actions-rs/toolchain@v1
      with:
        toolchain: ${{ steps.rust_toolchain.outputs.version }}
        override: true

I would use $GITHUB_OUTPUT though

[lklimek]

Superseded by #2070