Skip to content

Update version to 0.13.0#1584

Merged
jayconrod merged 1 commit intobazel-contrib:masterfrom
jayconrod:update-version
Jul 4, 2018
Merged

Update version to 0.13.0#1584
jayconrod merged 1 commit intobazel-contrib:masterfrom
jayconrod:update-version

Conversation

@jayconrod
Copy link
Collaborator

No description provided.

@jayconrod jayconrod requested a review from ianthehat July 3, 2018 21:39
@jayconrod jayconrod merged commit 3725f0a into bazel-contrib:master Jul 4, 2018
@jayconrod jayconrod deleted the update-version branch July 4, 2018 16:44
@wking
Copy link

wking commented Jul 6, 2018

Is this release missing a tag?

wking added a commit to wking/openshift-installer that referenced this pull request Jul 6, 2018
The most recent issue was bazel-contrib/rules_go#1393, which landed on
March 21st [1].  That code went out with rules_go v0.11.0:

  rules_go$ git log --oneline -1 361556b
  361556b Add go_binary out attribute for custom file names (openshift#1393)
  rules_go$ git describe --contains 361556b
  0.11.0~26

I'm bumping to 0.12.1 as the most-recent tagged release [2] (although
0.13.0 was cut two days ago, and seems to just be missing a tag [3]).

While I'm at it, I've bumped bazel-gazelle to it's most-recent tagged
release [4].  I'm not sure if the Bazel libraries are compatible
between minor releases, but they seem to be versioned together so
having 0.12.x versions of both seemed safest.

[1]: bazel-contrib/rules_go#1393 (comment)
[2]: https://github.com/bazelbuild/rules_go/releases
[3]: bazel-contrib/rules_go#1584 (comment)
[4]: https://github.com/bazelbuild/bazel-gazelle/releases
@jayconrod
Copy link
Collaborator Author

It's not quite released yet. See Release 0.13.0 is almost ready on the bazel-go-discuss mailing list. I expect to tag a release early next week.

yushan26 pushed a commit to yushan26/rules_go that referenced this pull request Jun 16, 2025
Many existing Python repos don't use `__main__.py` to indicate the the
main module. Instead, they put something like below in any Python files:

```python
if __name__ == "__main__":
  main()
```

This PR makes the Gazelle extension able to recognize main modules like
this, when `__main__.py` doesn't exist. This reduces the need to create
`__main__.py` when enabling Gazelle extensions in existing Python repos.

The current behavior of creating single `py_binary` for `__main__.py` is
preserved and takes precedence. So this is a backward-compatible change.

Closes bazel-contrib#1566.
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.

3 participants