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

Update revive to 0.1.0-dev.8 #21

Merged
merged 1 commit into from
Jan 20, 2025
Merged

Update revive to 0.1.0-dev.8 #21

merged 1 commit into from
Jan 20, 2025

Conversation

smiasojed
Copy link
Collaborator

No description provided.

@@ -14,7 +14,7 @@ spec:
spec:
containers:
- name: revive-remix-backend
image: paritytech/revive-remix-backend:1.3.5
image: paritytech/revive-remix-backend:1.3.6
Copy link
Member

Choose a reason for hiding this comment

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

What versioning is this following?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Now Minor update is the change in backend logic
Revive change is the Patch update

Copy link
Member

Choose a reason for hiding this comment

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

I think it would make sense to use the revive version in the tag? Then you don't need to do this when actually nothing changed: There can be multiple version of the revive-remix_backend but the images include different revive versions. As a side effect it's directly visible what compiler version is deployed too.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I think that it may be the last backend release, so probably it does not make sense to introduce any changes now.

@smiasojed smiasojed merged commit a1612a6 into main Jan 20, 2025
4 checks passed
@smiasojed smiasojed deleted the rel-dev.8 branch January 20, 2025 08:39
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.

2 participants