angular-docs-cn/dev-infra/release/versioning/BUILD.bazel

load("//dev-infra:defaults.bzl", "ts_library")

ts_library(
    name = "versioning",
    srcs = glob([
        "**/*.ts",
    ]),
    visibility = ["//dev-infra:__subpackages__"],
    deps = [
        "//dev-infra/release/config",
        "//dev-infra/utils",
        "@npm//@types/node-fetch",
        "@npm//@types/semver",
        "@npm//node-fetch",
        "@npm//semver",
    ],
)
build: update to rules_nodejs v4.0.0-beta.0 (#42760) Updates the Bazel NodeJS rules to v4.0.0-beta.0. This is necessary so that the Angular components repo can update, and it's generally good to stay as up-to-date as possible with the Bazel rules as it's easy to fall behind, and updating early allows us to discover issues affecting our tooling earlier (where they are easier to address due to e.g. potential breaking change policy). PR Close #42760 2021-07-06 09:45:55 -04:00			`load("//dev-infra:defaults.bzl", "ts_library")`
refactor(dev-infra): move common versioning tooling to shared location (#38656) We initially added logic for determining active release trains into the merge script. Given we now build more tools that rely on this information, we move the logic into a more general "versioning" folder that can contain common logic following the versioning document for the Angular organization. PR Close #38656 2020-09-09 08:42:34 -04:00
			`ts_library(`
			`name = "versioning",`
			`srcs = glob([`
			`"*/.ts",`
			`]),`
			`visibility = ["//dev-infra:__subpackages__"],`
			`deps = [`
			`"//dev-infra/release/config",`
			`"//dev-infra/utils",`
			`"@npm//@types/node-fetch",`
			`"@npm//@types/semver",`
			`"@npm//node-fetch",`
			`"@npm//semver",`
			`],`
			`)`