Skip to content

Announce rules_go v0.20.1, v0.19.7 [skip ci]#2253

Merged
jayconrod merged 1 commit intobazel-contrib:masterfrom
jayconrod:announce-releases
Oct 18, 2019
Merged

Announce rules_go v0.20.1, v0.19.7 [skip ci]#2253
jayconrod merged 1 commit intobazel-contrib:masterfrom
jayconrod:announce-releases

Conversation

@jayconrod
Copy link
Copy Markdown
Collaborator

Fixes #2250

@jayconrod jayconrod requested a review from ianthehat as a code owner October 18, 2019 02:15
@jayconrod jayconrod merged commit 214becd into bazel-contrib:master Oct 18, 2019
@jmillikin-stripe
Copy link
Copy Markdown
Contributor

FYI: The release page at https://github.com/bazelbuild/rules_go/releases/tag/v0.20.1 says "Go 1.12.10, 1.12.11, 1.13.2, and 1.13.3 are now supported.", but it looks like 1.12.12 is also supported.

@jayconrod
Copy link
Copy Markdown
Collaborator Author

@jmillikin-stripe Thanks, fixed. Too many releases to keep track of :P

@jayconrod jayconrod deleted the announce-releases branch October 18, 2019 13:44
yushan26 pushed a commit to yushan26/rules_go that referenced this pull request Jun 16, 2025
…l-contrib#2253)

With this change we set the default value of `--python_version` when
the `python.toolchain` is used in `bzlmod` and we generate the
appropriate config settings based on the registered toolchains and
given overrides by the root module.

This means that we expect the `--python_version` to be always set to
a non-empty value under `bzlmod` and we can cleanup code which was
handling `//conditions:default` case. This also means that we can
in theory drop the requirement for `python_version` in `pip.parse`
and just setup dependencies for all packages that we find in the
`requirements.txt` file and move on. This is left as future work
by myself or anyone willing to contribute. We can also start reusing
the same `whl_library` instance for multi-platform packages because
the python version flag is always set - this will simplify the layout
and makes the feature non-experimental anymore under bzlmod.

Summary:
* Add `@pythons_hub` to the `WORKSPACE` with dummy data to make
  pythons_hub work.
* Add `MINOR_MAPPING` and `PYTHON_VERSIONS` to pythons_hub to
  generate the config settings.
* Remove handling of the default version in `pypi` code under bzlmod.

Work towards bazel-contrib#2081, bazel-contrib#260, bazel-contrib#1708

---------

Co-authored-by: Richard Levasseur <rlevasseur@google.com>
yushan26 pushed a commit to yushan26/rules_go that referenced this pull request Jun 16, 2025
…major_minor (bazel-contrib#2275)

With this change the users can simply reuse our internal flag that will
correctly report the `X.Y` version in `select` statements. If users
previously depended on now removed `is_python_config_setting` now they
have an alternative.

Followup to bazel-contrib#2253
yushan26 pushed a commit to yushan26/rules_go that referenced this pull request Jun 16, 2025
…bazel-contrib#2350)

bazel-contrib#2253 broke how the config settings are generated and only generated the
config
setting values for the python version values that we would have the
registered
toolchains for. This PR restores the previous behaviour. However, if the
root
module uses `python.override` to remove the allowed toolchains, then
`config_settings` will be also affected.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Support Go 1.13.2, 1.13.3, 1.12.11, 1.12.12

3 participants