angular-cn/dev-infra/release/notes/BUILD.bazel

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

ts_library(
    name = "notes",
    srcs = glob([
        "**/*.ts",
    ]),
    visibility = ["//dev-infra:__subpackages__"],
    deps = [
        "//dev-infra/commit-message",
        "//dev-infra/release/config",
        "//dev-infra/release/versioning",
        "//dev-infra/utils",
        "@npm//@types/ejs",
        "@npm//@types/node",
        "@npm//@types/semver",
        "@npm//@types/yargs",
        "@npm//ejs",
        "@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 15:45:55 +02:00			`load("//dev-infra:defaults.bzl", "ts_library")`
refactor(dev-infra): move the release notes into its own directory under release (#42225) Move the release notes tooling under its own directory under release rather than within publish, in preparation to have a release note generation command for ad-hoc release note generation. PR Close #42225 2021-05-21 10:08:01 -07:00
			`ts_library(`
			`name = "notes",`
			`srcs = glob([`
			`"*/.ts",`
			`]),`
			`visibility = ["//dev-infra:__subpackages__"],`
			`deps = [`
			`"//dev-infra/commit-message",`
			`"//dev-infra/release/config",`
			`"//dev-infra/release/versioning",`
			`"//dev-infra/utils",`
			`"@npm//@types/ejs",`
			`"@npm//@types/node",`
			`"@npm//@types/semver",`
			`"@npm//@types/yargs",`
			`"@npm//ejs",`
			`"@npm//semver",`
			`],`
			`)`