Keith Smiley
Keith Smiley
@brentleyjones is going to investigate some incremental bundling behavior where we likely do something non-hermetic for the local-only use case to improve bundling performance and avoid some unnecessary bazel checks.
Currently these asset types are just ignored
Currently when you create a new app you have to jump through some hoops to deal with default entitlements / plist replacements that Xcode handles. We should either handle them...
As part of improving documentation we should throw a page in about the codesign performance facilities
There are some required flags, and some configuration environment variables we should document
These change overtime and are quite useful for local dev
Formalizing things discussed on https://github.com/bazelbuild/bazel/issues/14551
If you have a MODULE.bazel with something like: ```bzl archive_override( module_name = "apple_support", integrity = "sha256-O5jDzs0Q/DAfEGMWsZn1jBQ7VIQ0aQjgAUPl/skjIv4=", strip_prefix = "apple_support-65d28246a1b6d4f98549b364d8d5cf3cefe9758c", urls = [ "https://github.com/bazelbuild/apple_support/archive/65d28246a1b6d4f98549b364d8d5cf3cefe9758c.tar.gz", ], ) bazel_dep(name = "apple_support", version =...
Since [PEP 518](https://peps.python.org/pep-0518/) projects can specify their build system requirements in their pyproject.toml file. Currently this is not included in the pip-compile and therefore can lead to non-reproducible issues. This...