Tags: darkman1334/sway
Tags
Fix style guide example not using local std (FuelLabs#4721) ## Description Style guide example is blocking new releases because it tries to use an unpublished version of std ## Checklist - [x] I have linked to any relevant issues. - [x] I have commented my code, particularly in hard-to-understand areas. - [x] I have updated the documentation where relevant (API docs, the reference, and the Sway book). - [x] I have added tests that prove my fix is effective or that my feature works. - [x] I have added (or requested a maintainer to add) the necessary `Breaking*` or `New Feature` labels where relevant. - [x] I have done my best to ensure that my PR adheres to [the Fuel Labs Code Review Standards](https://github.com/FuelLabs/rfcs/blob/master/text/code-standards/external-contributors.md). - [x] I have requested a review from the relevant team or maintainers.
Remove duplicate type checker definitions in favor of `UnifyCheck` (F… …uelLabs#4593) ## Description This is based on FuelLabs#4184 and fuses all duplicate type subset checkers in favor of using `UnifyCheck` and `TypeInfo` equality. ## Checklist - [x] I have linked to any relevant issues. - [x] I have commented my code, particularly in hard-to-understand areas. - [x] I have updated the documentation where relevant (API docs, the reference, and the Sway book). - [x] I have added tests that prove my fix is effective or that my feature works. - [x] I have added (or requested a maintainer to add) the necessary `Breaking*` or `New Feature` labels where relevant. - [x] I have done my best to ensure that my PR adheres to [the Fuel Labs Code Review Standards](https://github.com/FuelLabs/rfcs/blob/master/text/code-standards/external-contributors.md). - [x] I have requested a review from the relevant team or maintainers. Co-authored-by: Marcos Henrich <marcoshenrich@gmail.com>
release: bump to v0.40.0 (FuelLabs#4601) ## Description Waiting for: - FuelLabs#4525. @Dhaiwat10 was waiting for a release with the linked PR merged. @IGI-111 I had the PR ready, leaving it up to you when to merge & cut the release. Made this a major bump as we had a breaking change merged (FuelLabs#4574). ## Checklist - [ ] I have linked to any relevant issues. - [ ] I have commented my code, particularly in hard-to-understand areas. - [ ] I have updated the documentation where relevant (API docs, the reference, and the Sway book). - [ ] I have added tests that prove my fix is effective or that my feature works. - [ ] I have added (or requested a maintainer to add) the necessary `Breaking*` or `New Feature` labels where relevant. - [ ] I have done my best to ensure that my PR adheres to [the Fuel Labs Code Review Standards](https://github.com/FuelLabs/rfcs/blob/master/text/code-standards/external-contributors.md). - [ ] I have requested a review from the relevant team or maintainers. Co-authored-by: IGI-111 <igi-111@protonmail.com>
Re-publish 0.37.2 as 0.38.0 due to breaking changes (FuelLabs#4494) See here for context: FuelLabs#4492 (comment) This follows a re-release of 0.37.1 as 0.37.3: https://github.com/FuelLabs/sway/releases/tag/v0.37.3 The outcome of all this is that ideally, users previously on 0.37.1 will now pull 0.37.3 next time they run `cargo update` and will not encounter any breakage. Those ready to update can point to 0.38.0 after this is published. Also runs `cargo update` in order to update deps to their latest patch release. --------- Co-authored-by: Joshua Batty <joshpbatty@gmail.com>
Republish v0.37.1 as v0.37.3 to avoid users encountering breaking cha… …nges Aimed at addressing the following comment: FuelLabs#4492 (comment) Currently our bot doesn't make it easy to yank existing releases. Here we just republish 0.37.1 as 0.37.3 to ensure users updating their sway repo deps don't consume the breaking changes accidentally included in 0.37.2.
PreviousNext