Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

dependencies: update Rust crates to use ring 0.17.x #6

Closed
wants to merge 7 commits into from

Conversation

reubenmiller
Copy link
Owner

Proposed changes

Update Rust crates to versions which use the newer ring 0.17.x release. ring 0.17.x makes it possible to compile thin-edge.io for different target triples (though it is still not possible via cargo-zigbuild).

Whilst the build tooling has not been updated to support building for the additional targets, it at least opens the possibility for users to build the project on the native architectures, or use their own setup which uses clang (an example can be seen from the ring workflow which shows how to build for multiple targest on a linux x86_64 host).

Note

A fork of the x509-parser crate was created due to a delay in a PR being merged due to the MSRV being changed for an optional feature (there is an ongoing discussion in the PR how this could be resolved, but it will take time)

Types of changes

  • Bugfix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Improvement (general improvements like code refactoring that doesn't explicitly fix a bug or add any new functionality)
  • Documentation Update (if none of the other choices apply)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)

Paste Link to the issue


Checklist

  • I have read the CONTRIBUTING doc
  • I have signed the CLA (in all commits with git commit -s)
  • I ran cargo fmt as mentioned in CODING_GUIDELINES
  • I used cargo clippy as mentioned in CODING_GUIDELINES
  • I have added tests that prove my fix is effective or that my feature works
  • I have added necessary documentation (if appropriate)

Further comments

dependabot bot and others added 7 commits January 29, 2024 07:26
Bumps [SebRollen/toml-action](https://github.com/sebrollen/toml-action) from 1.0.2 to 1.2.0.
- [Release notes](https://github.com/sebrollen/toml-action/releases)
- [Commits](SebRollen/toml-action@v1.0.2...v1.2.0)

---
updated-dependencies:
- dependency-name: SebRollen/toml-action
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
…tions/SebRollen/toml-action-1.2.0

build(deps): Bump SebRollen/toml-action from 1.0.2 to 1.2.0
Added a workaround for thin-edge#2584 by changing status update smartrest message
to 102.

Also fixed thin-edge#2606 by properly checking in the fs event handler if the
path of the event is actually inside the c8y operations path.

Signed-off-by: Marcel Guzik <[email protected]>
…wn-as-child-devices

fixed services shown as child devices thin-edge#2584
…target triples

Use a fork of x509-parser which bumps the MSRV as a PR with this update is pending due to complications with the bump in MSRV due to a dependency which is only required by the options "verify" feature. The fork can be removed once rusticata/x509-parser#148 has been merged.

Signed-off-by: Reuben Miller <[email protected]>
@reubenmiller reubenmiller force-pushed the dev-update-dependencies branch from 58d2e9c to 63042ef Compare January 29, 2024 15:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants