| commit | 4eea9c5aa15652908921c808885e3bd2e357a54a | [log] [tgz] |
|---|---|---|
| author | keertk <keerthanakumar@google.com> | Fri May 26 09:39:43 2023 +0000 |
| committer | GitHub <noreply@github.com> | Fri May 26 09:39:43 2023 +0000 |
| tree | 17f6332dddebabd1c5e26fbdbfc055cc108cc09a | |
| parent | 2d557b665c33fc52fb799d093b1f65493938185c [diff] |
[6.2.1] Update relnotes scripts (#18503) * Update relnotes scripts. 1. Update relnotes.sh to use relnotes.py to generate release notes if not a rolling release 2. Update relnotes.py: - Include co-authors in acknowledgements - Make sure older releases work with the correct "last" release - For minor/patch release, use commit message if no RELNOTES found - Add option to sort relnotes by category - Other minor fixes/updates PiperOrigin-RevId: 531628752 Change-Id: Ifdcf55d319e7221b7ed4eb7e510a3c4c9a88b41d * Updates/fixes to relnotes script - Replace removeprefix since this requires python 3.9 - Include authors/co-authors with @users.noreply.github.com in acknowledgement section (we're currently not adding contributors w/o public emails) PiperOrigin-RevId: 534091486 Change-Id: I455f96310062069148d2a28758e65f9f5675d3ff * Fix relnotes script - Update GitHub token retrieval - Allow checking out tags (final releases) in addition to branches (RCs) PiperOrigin-RevId: 534851155 Change-Id: I8b92898a8f5dd20139ca2467bb8604c6a8eabd67
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel rebuilds only what is necessary. With advanced local and distributed caching, optimized dependency analysis and parallel execution, you get fast and incremental builds.
One tool, multiple languages: Build and test Java, C++, Android, iOS, Go, and a wide variety of other language platforms. Bazel runs on Windows, macOS, and Linux.
Scalable: Bazel helps you scale your organization, codebase, and continuous integration solution. It handles codebases of any size, in multiple repositories or a huge monorepo.
Extensible to your needs: Easily add support for new languages and platforms with Bazel's familiar extension language. Share and re-use language rules written by the growing Bazel community.
Follow our tutorials:
To report a security issue, please email security@bazel.build with a description of the issue, the steps you took to create the issue, affected versions, and, if known, mitigations for the issue. Our vulnerability management team will respond within 3 working days of your email. If the issue is confirmed as a vulnerability, we will open a Security Advisory. This project follows a 90 day disclosure timeline.
See CONTRIBUTING.md
