Make bazel-remote packages consumable as a module #646
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Seems to work, although can't really tell for sure without d0d2a17 getting pushed into buchgr/bazel-remote. |
iangudger
approved these changes
Mar 6, 2023
The new import path is: github.com/buchgr/bazel-remote/v2 Warning: bazel-remote go packages do not follow semantic versioning rules, since it is primarily intended to be consumed as a standalone executable. I aim to maintain backwards compatibility for the standalone executable (within each major release), but provide no guarantees on the stability of the packages used internally. Relates to buchgr#635.
mostynb
force-pushed
the
module_consumability
branch
from
d0d2a17
to
8d472a9
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The new import path is:
github.com/buchgr/bazel-remote/v2
Warning: bazel-remote go packages do not follow semantic versioning rules, since it is primarily intended to be consumed as a standalone executable.
I aim to maintain backwards compatibility for the standalone executable (within each major release), but provide no guarantees on the stability of the packages used internally.
Relates to #635.