Skip to content

Releases: bazelbuild/bazel

0.4.3

22 Dec 12:37
Compare
Choose a tag to compare

Release 0.4.3 (2016-12-22)

Baseline: c645a45

Cherry picks:

  • af878d0: Add coverage support for java test. (series 4/4 of
    open-sourcing coverage command for java test)
  • 09b92a8: Rollback of commit
    67b4d52.
  • b11dd48: Fix bad bug with the parallel implementation of
    BinaryOperatorExpression. Turns out that
    ForkJoinTask#adapt(Callable) returns a ForkJoinTask
    whose Future#get on error throws a ExecutionException
    wrapping a RuntimeException wrapping the thrown checked
    exception from the callable. This is documented
    behavior [1] that I incorrectly didn't know about.
  • 9012bf1: Fix scripts/packages/convert_changelog to read the
    changelog correctly
  • 55c97bc: Release script: if master branch does not exist, fall
    back on origin/master
  • 4fb378c: Debian repository: override section and priority fields
  • acbcbc2: Fix release notes in emails
  • 4975760: Fix PathFragment to not use Java8-only static hashCode
    methods.
  • 05fd076: Disable sandboxing for XibCompile actions.

Incompatible changes:

  • Skylark maven_jar and maven_aar settings attribute is now a label
    so it can be checked into your workspace.
  • --{no}experimental_use_rclass_generator is now a nop.

New features:

  • Coverage support (experimental) for pure Java target.
    Use bazel coverage //my:target to generate coverage information
    from a java_test.

Important changes:

  • Enable fallback URLs in Skylark http rules.
  • cc_proto_library generates C++ code from proto_library rules.
  • cc_library now supports the strip_prefix and strip_include_prefix
    attributes for control of include paths.
  • Skylark dicts internally don't rely on keys order anymore and
    accept any hashable values (i.e. structs with immutable values)
    as keys. Iteration order of dictionaries is no longer specified.

Notice: Bazel installers contain binaries licensed under the GPLv2 with
Classpath exception. Those installers should always be redistributed along with
the source code.

Security: All our binaries are signed with our
public key 48457EE0.

0.4.2

07 Dec 18:54
Compare
Choose a tag to compare

Release 0.4.2 (2016-12-02)

Baseline: 6331a94

Cherry picks:

  • 7b835d9: Do not patch WORKSPACE in the release process

Incompatible changes:

  • Callback functions in Skylark no longer support the cfg
    parameter. This is a cleanup and only affects the signatures of
    callbacks, since the parameter hasn't been set since September
    2016.

Important changes:

  • Alias proto_library's produce a descriptor set that contains all
    srcs of its dependencies.
  • proto_library supports strict proto deps.
  • Top level @AndroidSDK support library targets have been replaced
    by @androidsdk//:- for Android
    SDK Support and Google Play Services libraries.

Notice: Bazel installers contain binaries licensed under the GPLv2 with
Classpath exception. Those installers should always be redistributed along with
the source code.

Security: All our binaries are signed with our
public key 48457EE0.

0.4.1

30 Nov 09:23
Compare
Choose a tag to compare

Release 0.4.1 (2016-11-21)

Baseline: 2a26c3c

Cherry picks:

  • a79581e: Add gpu compile support to MSVC wrapper script

New features:

  • android_library now has a "exported_plugins" attribute just like
    java_library
  • Use --strict_system_includes to apply hdrs_check=strict also to
    cc_library.includes, even if sandboxing is disabled.
  • Bazel on Windows: java_binary can now be the executable of
    Skylark rule actions (ctx.action's executable argument)
  • Packages are defined in BUILD.bazel as well as BUILD files.

Important changes:

  • getattr()'s 3-arg form no longer raises an error when the
    retrieved field is a built-in method.
  • --apk_signing_method default changed to v1. Android APKs are now
    signed with the new ApkSignerTool by default.
  • New rule: proto_lang_toolchain(), to support LANG_proto_library
    rules on multiple platforms.
  • Fix for Android clang++ std::stack segfault on 32bit x86. See
    https://code.google.com/p/android/issues/detail?id=220159
  • Default android_manifest_merger is now "android" which uses the
    official Android manifest merger.
    http://tools.android.com/tech-docs/new-build-system/user-guide/man
    ifest-merger
  • Do not propagate aspect to its own attributes when using '*'.
  • Comparing sets (if set1 < set2:) is not allowed anymore in
    Skylark because it didn't work correctly anyway.
  • When --experimental_extra_action_top_level_only, Bazel reports
    extra-actions for actions registered by Aspects injected by a
    top-level rule (approximately).
  • Blacklists for proto_lang_toolchain() no longer have to be
    proto_library's.
  • Extra actions now contain aspect-related information.
  • Fix slicing bug where "abc"[:-4:-1] would give wrong answer

Notice: Bazel installers contain binaries licensed under the GPLv2 with
Classpath exception. Those installers should always be redistributed along with
the source code.

Security: All our binaries are signed with our
public key 48457EE0.

0.4.0

02 Nov 18:03
Compare
Choose a tag to compare

Release 0.4.0 (2016-10-26)

Baseline: 088bbc6

Cherry picks:

  • b01160c: Stamp Windows release.
  • 2d6736e: Add --no-tty for gpg signing
  • 9b1dfb8: Remove .sig file before gpg signing
  • 81aede1: Reimplement whole archive on Windows

Incompatible changes:

  • Skylark: updating list/dicts while they are being looped over is not
    allowed. Use an explicit copy if needed ("for x in list(mylist):").
  • Bazel now uses the --cpu flag to look up Jvms; it falls back
    to "default" if it can't find a Jvm matching the CPU value.
  • --command_port=-1 to use AF_UNIX for client/server communications
    is not supported anymore.
  • Sandboxed actions can access the network by default, unless their
    target has a "block-network" tag.

New features:

  • Files now have an "extension" property in Skylark.

Important changes:

  • Added a new flag --sandbox_tmpfs_path, which asks the sandbox to
    mount an empty, writable directory at a specified path when
    running actions. (Supported on Linux only for now.)
  • Update protoc-3.0.0-mingw.exe to a working (statically linked)
    binary
  • apple_static_library rule to create multi-architecture static
    archive files from Objc/C++/Swift dependencies on apple platforms
  • JS: Add support for localization with closure managed rules.
  • Create a flag --android_dynamic_mode to turn off dynamic mode
    during the Android split transition.
  • Darwin sandboxing is default.
  • Remove flag --experimental_zip_tree_artifact from j2objc Java
    annotation processing support.
  • A few functions are added to BUILD files for consistency (hash,
    dir,
    hasattr, getattr) with .bzl files, although they are not very
    useful.
  • --watchfs is now a command option; the startup option of the same
    name is deprecated. I.e., use bazel build --watchfs, not
    blaze --watchfs
    build.

Notice: Bazel installers contain binaries licensed under the GPLv2 with
Classpath exception. Those installers should always be redistributed along with
the source code.

Security: All our binaries are signed with our
public key.

0.3.2

07 Oct 17:33
Compare
Choose a tag to compare

Release 0.3.2 (2016-10-07)

Baseline: 023a7bd

Cherry picks:

  • bebbbe5: Fix dependency on libtool's helper script
    make_hashed_objlist.py.
  • 8a0d45f: Add the version information to the bazel.exe file
  • 2bc0939: Allow new_ rules to overwrited BUILD files in
    downloaded repos
  • c5545fd: Rollback of commit
    96d4628.
  • eb87208: Make cc_configure on Windows more robust
  • c30432c: Fix cc_configure on Windows
  • 95b16a8: sandbox: Replace the error-prone lazy cleanup of
    sandbox directories by a simple synchronous cleanup.
  • e898023: Fix #1849: Sandboxing on OS X should be turned off by
    default for 0.3.2.
  • ffdc05d: Add action_config and feature for linking on Windows

Incompatible changes:

  • If you maintain a rule that uses persistent workers, you'll have
    to specify execution_requirements={"supports-workers": 1} in the
    ctx.action that intends to run a tool with workers. The
    WorkerSpawnStrategy will alert you with a warning message if you
    forget to make this change and fallback to non-worker based
    execution.
  • It is now an error to include a precompiled library (.a, .lo, .so)
    in a cc_library which would generate a library with the same name
    (e.g., libfoo.so in cc_library foo) if that library also contains
    other linkable
    sources.
  • The main repository's execution root is under the main
    repository's workspace name, not the source directory's basename.
    This shouldn't
    have any effect on most builds, but it's possible it could break
    someone doing
    weird things with paths in actions.
  • Blaze doesn't support Unix domain sockets for communication
    between its client and server anymore. Therefore, the
    --command_port command line argument doesn't accept -1 as a valid
    value anymore.
  • Skylark: It is an error to shadow a global variable with a local
    variable after the global has already been accessed in the
    function.
  • bin_dir and genfiles_dir are now properties of ctx, not
    configuration. That is, to access the bin or genfiles directory
    from a
    Skylark rule, use ctx.bin_dir or ctx.genfiles_dir (not
    ctx.configuration.{bin,genfiles}_dir). At the moment, you can
    access
    {bin,genfiles}_dir from either, but the ctx.configuration version
    will
    stop working in a future release.
  • filegroup-based C++ toolchains are not supported anymore.
    --*_crosstool_top options must always point to a
    cc_toolchain_suite rule (or an alias of one).
  • repository_ctx.{download,download_and_extract,execute} API now use
    named parameters for optional parameters and no
    longer uses argument
    type to distinguished between arguments
    (executable attribute name
    must be specified when preceding optional
    arguments are missing).

New features:

  • print and fail are now available in BUILD files.

Important changes:

  • Added @bazel_tools//tools/build_defs/repo/git.bzl as a Skylark
    rule for Git repositories.
  • Added @bazel_tools//tools/build_defs/repo/maven_rules.bzl as a
    Skylark rule for Maven repositories.
  • Add global hash() function for strings (only)
  • Improve Android split transition handling.
  • Removes exports_manifest attribute from android_binary rule.
  • java_proto_library: control strict-deps through a rule-level and
    a package-level attribute.
  • Persistent workers are now used by default for Java compilation
    in Bazel, which should speed up your Java builds by ~4x. You can
    switch back to the old behavior via --strategy=Javac=standalone.
    Check out http://www.bazel.io/blog/2015/12/10/java-workers.html
    for more details.
  • objc_* rules can now depend on any target that returns an "objc"
    provider.
  • Adds support for NDK12 to android_ndk_repository rule in Bazel.
  • Test targets can disable the JUnit4 test security manager via a
    property.
  • Disable the Android split transition if --android_cpu and
    fat_apk_cpu are both empty.
  • New sandboxing implementation for Linux in which all actions run
    in a separate execroot that contains input files as symlinks back
    to the originals in the workspace. The running action now has
    read-write access to its execroot and /tmp only and can no longer
    write in arbitrary other places in the file system.
  • Add worker support to single jar.
  • Invoke source jar action as a worker.
  • Sandboxed builds allow network access for builds by default.
    Tests will still be run without networking, unless
    "requires-network" is specified as a tag.
  • Add path.realpath() method for Skylark repositories.
  • On Mac devices, detect locally installed versions of xcode to:
    1. Use a sensible default if xcode is required but
      --xcode_version is unspecified.
    2. Use sensible default iOS SDK version for the targeted version
      of xcode if ios_sdk_version is unspecified.
  • Emacs' [C-x `], a.k.a. next-error, works again in emacsen >= 25.1
  • swift_library can be used to build watchOS apps.
  • Exposes the is_device field on Apple platform objects and adds
    the apple_common.platform_type(name) method to retrieve a
    platform_type value that can be passed to methods like the Apple
    fragment's multi_arch_platform.
  • Move Skylark git_repository rules to git.bzl
  • Add support for aspects to attr.label() attributes
  • Global varaiables HOST_CFG and DATA_CFG are deprecated in favor
    of strings "host"
    and "data.
    Argument cfg = "host" or cfg = "data" is mandatory if
    executable = True is provided for a label.
  • The deprecation attribute of all rules now causes warnings
    to be printed when other targets depend on a target with that
    attribute set.
  • Change default of --[no]instrument_test_targets to false, change
    default --instrumentation_filter (which previously tried to
    exclude test targets by heuristic) to only exclude targets in
    javatests.
  • Remove deprecated absolute paths in blaze IDE artifacts
  • When using android_binary.manifest_merger="android" the merger
    produces a summary log next to the merged manifest artifact.
  • Allow different default mallocs per configuration.

Notice: Bazel installers contain binaries licensed under the GPLv2 with
Classpath exception. Those installers should always be redistributed along with
the source code.

0.3.1

29 Jul 09:43
Compare
Choose a tag to compare

Release 0.3.1 (2016-07-29)

Baseline: 792a9d6

Cherry picks:

  • 25e5995: Rollback of commit
    a277033.
  • 2479405: Fix NPE with unset maven_jar sha1
  • 3cf2126: Rewrite the extra action info files if the data within
    them changes.
  • 5a9c6b4: JavaBuilder: Reintroduce the -extra_checks flag.

Incompatible changes:

  • Removed predefined Python variable "generic_cpu".
  • Skylark rules: if you set "outputs" or an attribute to a
    function, this function must now list its required attributes as
    parameters (instead of an attribute map).
  • The host_platform and target_platform entries are not written to
    the master log anymore.
  • Bazel requires Hazelcast 3.6 or higher now for remote execution
    support, because we upgraded our client library and the protocol
    it uses is incompatible with older versions.

New features:

  • LIPO context (--lipo_context) can now also be a cc_test (in
    addition to cc_binary)

Important changes:

  • If --android_crosstool_top is set, native code compiled for
    android will always use --android_compiler and not --compiler in
    choosing the crosstool toolchain, and will use --android_cpu if
    --fat_apk_cpu is not set.
  • Add --instrument_test_targets option.
  • apple_binary supports a new platform_type attribute, which, if
    set to "watchos", will build dependencies for Apple's watchOS2.
  • objc_binary now supports late-loaded dynamic frameworks.
  • Native Swift rules no longer pull in module maps unconditionally.
    Use --experimental_objc_enable_module_maps for that.
  • Merged manifests are guaranteed to have the application element
    as the last child of the manifest element as required by Android
    N.
  • The Android manifest merger is now available as an option for
    android_binary rules. The merger will honor tools annotations in
    AndroidManifest.xml and will perform placeholder substitutions
    using the values specified in android_binary.manifest_values. The
    merger may be selected by setting the manifest_merger attribute
    on android_binary.
  • The progress message would not clear packages that need to be
    loaded twice.
  • Remove warning for high value of --jobs.
  • Use the correct build configuration for shared native deps during
    Android split transitions.
  • When building ObjectiveC++, pass the flag -std=gnu++11.
  • use xcrun simctl instead of iossim to launch the app for "blaze
    run".
  • Glob arguments 'exclude' and 'exclude_directories' must be named
  • Bazel no longer regards an empty file as changed if its mtime has
    changed.

Notice: Bazel installers contain binaries licensed under the GPLv2 with
Classpath exception. Those installers should always be redistributed along with
the source code.

0.3.0

10 Jun 12:29
Compare
Choose a tag to compare

Release 0.3.0 (2016-06-10)

Baseline: a9301fa

Cherry picks:

  • ff30a73: Turn --legacy_external_runfiles back on by default
  • aeee3b8: Fix delete[] warning on fsevents.cc

Incompatible changes:

  • The --cwarn command line option is not supported anymore. Use
    --copt instead.

New features:

  • On OSX, --watchfs now uses FsEvents to be notified of changes
    from the filesystem (previously, this flag had no effect on OS X).
  • add support for the '-=', '*=', '/=', and'%=' operators to
    skylark. Notably, we do not support '|=' because the semantics
    of skylark sets are sufficiently different from python sets.

Important changes:

  • Use singular form when appropriate in blaze's test result summary
    message.
  • Added supported for Android NDK revision 11
  • --objc_generate_debug_symbols is now deprecated.
  • swift_library now generates an Objective-C header for its @objc
    interfaces.
  • new_objc_provider can now set the USES_SWIFT flag.
  • objc_framework now supports dynamic frameworks.
  • Symlinks in zip files are now unzipped correctly by http_archive,
    download_and_extract, etc.
  • swift_library is now able to import framework rules such as
    objc_framework.
  • Adds "jre_deps" attribute to j2objc_library.
  • Release apple_binary rule, for creating multi-architecture
    ("fat") objc/cc binaries and libraries, targeting ios platforms.
  • Aspects documentation added.
  • The --ues_isystem_for_includes command line option is not
    supported anymore.
  • global function 'provider' is removed from .bzl files. Providers
    can only be accessed through fields in a 'target' object.

Notice: Bazel installers contain binaries licensed under the GPLv2 with
Classpath exception. Those installers should always be redistributed along with
the source code.

0.2.3

17 May 14:33
Compare
Choose a tag to compare

Release 0.2.3 (2016-05-10)

Baseline: 5a2dd7a

Incompatible changes:

  • All repositories are now directly under the x.runfiles directory
    in the runfiles tree (previously, external repositories were at
    x.runfiles/main-repo/external/other-repo. This simplifies
    handling remote repository runfiles considerably, but will break
    existing references to external repository runfiles.
    Furthermore, if a Bazel project does not provide a workspace name
    in the WORKSPACE file, Bazel will now default to using main
    as the workspace name (instead of "", as previously). The
    repository's runfiles will appear under x.runfiles/main/.
  • Bazel does not embed protocol buffer-related rules anymore.
  • It is now an error for a cc rule's includes attribute to point to
    the workspace root.
  • Bazel warns if a cc rule's includes attribute points out of
    third_party.
  • Removed cc_* attributes: abi / abi_deps. Use select() instead.

New features:

  • select({"//some:condition": None }) is now possible (this "unsets"
    the attribute).

Important changes:

  • java_import now allows its 'jars' attribute to be empty.
  • adds crunch_png attribute to android_binary
  • Replace --java_langtools, --javabuilder_top, --singlejar_top,
    --genclass_top, and --ijar_top with
    java_toolchain.{javac,javabuilder,singlejar,genclass,ijar}
  • External repository correctness fix: adding a new file/directory
    as a child of a new_local_repository is now noticed.
  • iOS apps are signed with get-task-allow=1 unless building with -c
    opt.
  • Generate debug symbols (-g) is enabled for all dbg builds of
    objc_ rules.
  • Bazel's workspace name is now io_bazel. If you are using Bazel's
    source as an external repository, then you may want to update the
    name you're referring to it as or you'll begin seeing warnings
    about name mismatches in your code.
  • Fixes integer overflow in J2ObjC sources to be Java-compatible.
  • A FlagPolicy specified via the --invocation_policy flag will now
    match the current command if any of its commands matches any of
    the commands the current command inherits from, as opposed to
    just the current command.
  • The key for the map to cc_toolchain_suite.toolchains is now a
    string of the form "cpu|compiler" (previously, it was just "cpu").
  • Fix interaction between LIPO builds and C++ header modules.
  • Ctrl-C will now interrupt a download, instead of waiting for it to
    finish.
  • Proxy settings can now be specified in http_proxy and https_proxy
    environment variables (not just HTTP_PROXY and HTTPS_PROXY).
  • Skylark targets can now read include directories from
    ObjcProvider.
  • Expose parameterized aspects to Skylark.
  • Support alwayslink cc_library dependencies in objc binaries.
  • Import cc_library dependencies in generated Xcode project.

0.2.2b

25 Apr 08:35
Compare
Choose a tag to compare

Release 0.2.2b (2016-04-22)

Baseline: 759bbfe

Cherry picks:

  • 1250fda: Rollback of commit
    3514756.
  • ba8700e: Correctly set up build variables for the correct pic
    mode for fake_binary rules.
  • 386f242: Automated [] rollback of commit
    525fa71.
  • 97e5ab0: Fix cc_configure include path for Frameworks on OS X.
  • a20352e: cc_configure: always add -B/usr/bin to the list of gcc
    option
  • 0b26f44: cc_configure: Add piii to the list of supported
    cpu_value
  • 3e4e416: cc_configure: uses which on the CC environment variable
  • aa3dbd3: cc_configure.bzl: strip end of line when looking for
    the cpu
  • 810d60a: cc_configure: Add -B to compiler flag too

Patch release, only includes fixes to C++ auto-configuration.

0.2.2

21 Apr 13:20
Compare
Choose a tag to compare

Release 0.2.2 (2016-04-14)

Baseline: 759bbfe

  • 1250fda: Rollback of commit
    3514756.
  • ba8700e: Correctly set up build variables for the correct pic
    mode for fake_binary rules.
  • 386f242: Automated [] rollback of commit
    525fa71.

New features:

  • --extra_entitlements allows passing additional entitlements for
    iOS signing
  • The output of -printconfiguration of proguard is available
    through an implicit "[target_name]_proguard.confg" output of
    android_binary (and
    java_binary).
  • Objective-C compiler information is now available to Skylark.

Important changes:

  • ProGuard relies on bazel to check to see if the inputs have
    changed.
  • Build the jsonnet tool for the host when cross-compiling.
  • Add ProductType for watch OS 1 extension and application.
  • Restrict file types used for "entitlements" attribute to
    [".entitlements", ".plist"]
  • Restrict file types allowed for "strings" attribute to ".strings".
  • local_repository can take a relative path.
  • Support apple_watch1_extension and apple_watch_extension_binary
    rules for creating watch OS 1 extensions.
  • implement list.insert for skylark rule
  • Enable overriding attributes for Rust binaries.
  • ios_device attribute "xcode", for declaring a specific xcode to
    use when selecting iOS simulators.