build: remove various gulp build setup leftovers

scripts/circleci/publish-snapshots.sh

@@ -8,9 +8,9 @@ cd $(dirname ${0})/../..
 
 # Deploy build artifacts to the GitHub build repositories. The release output is already
 # fetched from the CircleCI workspace storage.
-./scripts/deploy/publish-build-artifacts.sh --no-build
+./scripts/deploy/publish-build-artifacts.sh
 
 # Deploy the docs content to the Github repository. We don't want to build the examples
 # package here again because it's already fetched from the CircleCI workspace storage.
-./scripts/deploy/publish-docs-content.sh --no-build
+./scripts/deploy/publish-docs-content.sh
 

scripts/deploy/publish-build-artifacts.sh

@@ -56,11 +56,6 @@ publishPackage() {
 
   echo "Starting publish process of ${packageName} for ${buildVersionName} into ${branchName}.."
 
-  if [[ ! ${COMMAND_ARGS} == *--no-build* ]]; then
-    # Create a release of the current repository.
-    $(npm bin)/gulp ${packageName}:build-release:clean
-  fi
-
   # Prepare cloning the builds repository
   rm -rf ${repoDir}
   mkdir -p ${repoDir}

src/bazel-tsconfig-build.json

@@ -1,8 +1,6 @@
 // TypeScript configuration that will be used to build entry-points of the CDK. To avoid
 // duplicate logic, we decided to just have one package-wide tsconfig file that will be
-// used by Bazel to build the sources for an entry-point. This means that we no longer
-// need multiple tsconfig files (build & test) for each entry-point once Bazel replaces
-// our gulp build system.
+// used by Bazel to build the sources for an entry-point.
 {
   "compilerOptions": {
     "baseUrl": ".",
@@ -35,8 +33,6 @@
     "types": ["tslib"]
   },
   "bazelOptions": {
-    // Note: We can remove this once we fully switched away from Gulp. Currently we still set
-    // some options here just in favor of the standard tsconfig's which extending this one.
     "suppressTsconfigOverrideWarnings": true
   }
 }

src/material-experimental/mdc-helpers/_mdc-helpers.scss

@@ -1,6 +1,5 @@
 // TODO(mmalerba): this file should be split into separate cohesive partials for things like
-//  "theming", "typography", "core". Currently splitting it is difficult because of our brittle
-//  gulp-based release build process. We can update this when we switch to bazel.
+//  "theming", "typography", "core".
 
 @use '@material/feature-targeting' as mdc-feature-targeting;
 @use '@material/typography' as mdc-typography;