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

Bump dep on semver to 1.0.0 #427

Merged
merged 3 commits into from
Aug 25, 2021
Merged

Conversation

illicitonion
Copy link
Collaborator

No description provided.

@illicitonion illicitonion requested a review from acmcarther as a code owner July 8, 2021 15:25
@illicitonion illicitonion force-pushed the semver-1 branch 3 times, most recently from 203f065 to c3b1a3b Compare July 9, 2021 10:38
Copy link
Collaborator

@dfreese dfreese left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. If you don't mind, I might wait on #425. I had a minor comment there, and then I think it's good to go.

@dfreese
Copy link
Collaborator

dfreese commented Aug 9, 2021

@illicitonion sorry for the delay on that, but #425 has been merged.

@illicitonion illicitonion force-pushed the semver-1 branch 2 times, most recently from 07818b7 to 9611ed9 Compare August 9, 2021 18:45
if self.metadata_template.is_none() {
return None;
}
self.metadata_template.as_ref()?;
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you store this to a value and use it later on line 532? That'll remove both the unwrap in those lines, and make the intent of this more clear.

Copy link
Collaborator

@dfreese dfreese left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like it's breaking the bazel build of this by not having serde-derive as a proc macro dependency? I'm not super familiar with the bazel build for this, but does something need to be regenerated? @UebelAndre, not sure if you'd see an obvious thing right away here.

Overall, looks good to me, though.

@UebelAndre
Copy link
Collaborator

Yes, if the dependencies are updated, then cargo-raze will need to be re-bootstrapped

bazel run //tools:bootstrap

Then commit the results and things should be good.

PS: @dfreese Can you check slack?

@illicitonion
Copy link
Collaborator Author

Yay, rebasing past #441 fixed CI :)

@illicitonion illicitonion merged commit 984f804 into google:main Aug 25, 2021
@illicitonion illicitonion deleted the semver-1 branch August 25, 2021 10:31
illicitonion pushed a commit that referenced this pull request Jun 24, 2022
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