[PROD RELEASE V6] #1702

kkartunov · 2025-11-02T05:38:45Z

No description provided.

…cted payment logic

…er-v6 Feat/challenge reviewer v6

…nto v6

V6 -> develop

fix(PM-2609): show respective scorecard types for respective review type

fix(PM-2609): lint error

…point Review"

fix(PM-2609): get only active scorecards

fix(PM-2640): copilot url in WM

src/components/LegacyLinks/index.js

-      )
+      {/* Always show Review link for v5 challenges using v5 ID */}
+      <>
+        <a href={reviewUrl} target={'_blank'} rel='noopener noreferrer' onClick={onClick}>Review</a>


To fix this issue, we should ensure that the value used for the challenge.id in the URL is strictly sanitized and/or type-checked as a valid non-malicious identifier before using it in the anchor's href attribute.

The best fix is to:

Coerce challenge.id to a string containing only safe characters appropriate for an identifier. Since IDs are typically numbers, we should ensure only numeric data is passed through, e.g. using Number(challenge.id) or a more robust parsing such as parseInt.

Alternatively, explicitly encode the URI component portion containing challenge.id via encodeURIComponent, which ensures any unexpected input is safely escaped for use in the URL.

Apply this fix within src/components/LegacyLinks/index.js, at the point where reviewUrl is constructed.

No new methods are needed; you can use JavaScript's built-in encodeURIComponent.

github-actions · 2025-11-02T05:38:59Z

.circleci/config.yml

  name: Installation of install_deploysuite.
  command: |
-    git clone --branch v1.4.15 https://github.com/topcoder-platform/tc-deploy-scripts ../buildscript
+    git clone --branch v1.4.17 https://github.com/topcoder-platform/tc-deploy-scripts ../buildscript


[❗❗ correctness]
The branch version for tc-deploy-scripts has been updated from v1.4.15 to v1.4.17. Ensure that this new version is compatible with the rest of the deployment scripts and does not introduce breaking changes.

github-actions · 2025-11-02T05:38:59Z

.circleci/config.yml

        ./awsconfiguration.sh $DEPLOY_ENV
-        ./buildenv.sh -e $DEPLOY_ENV -b ${LOGICAL_ENV}-${APPNAME}-buildvar
+        #./buildenv.sh -e $DEPLOY_ENV -b ${LOGICAL_ENV}-${APPNAME}-buildvar
+        source awsenvconf


[❗❗ correctness]
The buildenv.sh script has been commented out and replaced with psvar-processor.sh. Verify that psvar-processor.sh provides all necessary environment configurations previously handled by buildenv.sh to avoid missing configurations.

github-actions · 2025-11-02T05:38:59Z

.circleci/config.yml

-        ./master_deploy.sh -d ECS -e $DEPLOY_ENV -t latest -s ${LOGICAL_ENV}-global-appvar,${LOGICAL_ENV}-${APPNAME}-appvar -i ${APPNAME} -p FARGATE
+        #./buildenv.sh -e $DEPLOY_ENV -b ${LOGICAL_ENV}-${APPNAME}-deployvar
+        #source buildenvvar
+        ./psvar-processor.sh -t appenv -p /config/${APPNAME}/deployvar


[❗❗ correctness]
The buildenv.sh script has been commented out and replaced with psvar-processor.sh. Ensure that psvar-processor.sh correctly sets up the environment variables needed for deployment, as this change could affect the deployment process.

github-actions · 2025-11-02T05:38:59Z

.circleci/config.yml

+        ./psvar-processor.sh -t appenv -p /config/${APPNAME}/deployvar
+        source deployvar_env
+        #./master_deploy.sh -d ECS -e $DEPLOY_ENV -t latest -s ${LOGICAL_ENV}-global-appvar,${LOGICAL_ENV}-${APPNAME}-appvar -i ${APPNAME} -p FARGATE
+        ./master_deploy.sh -d ECS -e $DEPLOY_ENV -t latest -j /config/common/global-appvar,/config/${APPNAME}/appvar -i ${APPNAME} -p FARGATE


[❗❗ correctness]
The master_deploy.sh command now uses a different set of parameters for the -j option. Confirm that the new paths /config/common/global-appvar,/config/${APPNAME}/appvar are correct and accessible during deployment.

github-actions · 2025-11-02T05:38:59Z

.circleci/config.yml

        ./awsconfiguration.sh $DEPLOY_ENV
-        ./buildenv.sh -e $DEPLOY_ENV -b ${LOGICAL_ENV}-${APPNAME}-buildvar
+        #./buildenv.sh -e $DEPLOY_ENV -b ${LOGICAL_ENV}-${APPNAME}-buildvar
+        ./psvar-processor.sh -t appenv -p /config/${APPNAME}/buildvar


[❗❗ correctness]
The buildenv.sh script has been commented out in the smoke testing configuration. Ensure that psvar-processor.sh provides all necessary environment configurations previously handled by buildenv.sh to avoid missing configurations during smoke tests.

github-actions · 2025-11-02T05:39:00Z

.circleci/config.yml

          filters: &filters-dev
            branches:
-              only: ["develop", "PM-803_wm-regression-fixes", "PM-902_show-all-projects-on-challenge-page", "pm-1365"]
+              only: ["develop"]


[⚠️ maintainability]
The branch filter for development builds has been changed to only include the develop branch. Ensure this aligns with the intended workflow and that no other branches should trigger development builds.

github-actions · 2025-11-02T05:39:03Z

.github/workflows/trivy.yaml

+
+permissions:
+  contents: read
+  security-events: write


[❗❗ security]
The security-events: write permission is quite broad. Ensure that this level of access is necessary, as it could pose a security risk if not properly justified.

github-actions · 2025-11-02T05:39:04Z

.github/workflows/trivy.yaml

+jobs:
+  trivy-scan:
+    name: Use Trivy
+    runs-on: ubuntu-24.04


[⚠️ maintainability]
Consider using a stable or LTS version of Ubuntu (e.g., ubuntu-latest or ubuntu-22.04) to ensure long-term support and stability for the workflow.

github-actions · 2025-11-02T05:39:04Z

.github/workflows/trivy.yaml

+          ignore-unfixed: true
+          format: "sarif"
+          output: "trivy-results.sarif"
+          severity: "CRITICAL,HIGH,UNKNOWN"


[⚠️ correctness]
The severity levels include UNKNOWN, which might lead to unexpected results. Ensure this is intentional and aligns with your security policy.

github-actions · 2025-11-02T05:39:04Z

.github/workflows/trivy.yaml

+          output: "trivy-results.sarif"
+          severity: "CRITICAL,HIGH,UNKNOWN"
+          scanners: vuln,secret,misconfig,license
+          github-pat: ${{ secrets.GITHUB_TOKEN }}


[❗❗ security]
Ensure that the GITHUB_TOKEN has the necessary permissions and is securely managed, as it is used to authenticate the Trivy scanner.

github-actions · 2025-11-02T05:39:06Z

.gitignore

 *.env
 *.pem
 *.vscode
+*.pem


[💡 maintainability]
The entry *.pem is duplicated. Consider removing the duplicate to maintain clarity and avoid confusion.

github-actions · 2025-11-02T05:39:07Z

.gitignore

 *.pem
 *.vscode
+*.pem
+*.vscode


[💡 maintainability]
The entry *.vscode is duplicated. Consider removing the duplicate to maintain clarity and avoid confusion.

docker/Dockerfile

@@ -1,5 +1,5 @@
-# Use the base image with Node.js
-FROM node:12
+# Use Node.js 22 base image


github-actions · 2025-11-02T05:39:11Z

build.sh

+else
+  # Compare lockfile from container with local copy
+  cp "$LOCK_FILE_NAME" ".old-$LOCK_FILE_NAME"
+  docker cp "app:/$APP_NAME/$LOCK_FILE_NAME" "$LOCK_FILE_NAME"


[⚠️ correctness]
Consider checking the exit status of docker cp to ensure the lockfile is copied successfully. This will help avoid silent failures if the copy operation fails.

github-actions · 2025-11-02T05:39:11Z

build.sh

-fi
+if [ "$UPDATE_CACHE" -eq 1 ]; then
+  echo "Lockfile changed or node_modules missing; refreshing local node_modules from container..."
+  rm -rf node_modules


[⚠️ security]
The use of rm -rf node_modules is potentially dangerous as it will forcefully remove the directory without confirmation. Ensure that this is the intended behavior and that there are no unintended side effects.

github-actions · 2025-11-02T05:39:14Z

config/constants/development.js

+  CHALLENGE_PHASES_URL: `${DEV_API_HOSTNAME}/v6/challenge-phases`,
+  CHALLENGE_TIMELINES_URL: `${DEV_API_HOSTNAME}/v6/challenge-timelines`,
+  COPILOTS_URL: 'https://copilots.topcoder-dev.com',
  PROJECT_API_URL: `${DEV_API_HOSTNAME}/v5/projects`,


[⚠️ correctness]
The PROJECT_API_URL is still using the /v5 endpoint, while other similar URLs have been updated to /v6. Verify if this is intentional or if it should be updated to maintain consistency.

github-actions · 2025-11-02T05:39:14Z

config/constants/development.js

  PROJECT_API_URL: `${DEV_API_HOSTNAME}/v5/projects`,
-  GROUPS_API_URL: `${DEV_API_HOSTNAME}/v5/groups`,
+  GROUPS_API_URL: `${DEV_API_HOSTNAME}/v6/groups`,
  TERMS_API_URL: `${DEV_API_HOSTNAME}/v5/terms`,


[⚠️ correctness]
The TERMS_API_URL is still using the /v5 endpoint, while other similar URLs have been updated to /v6. Verify if this is intentional or if it should be updated to maintain consistency.

github-actions · 2025-11-02T05:39:17Z

config/constants/index.js

@@ -1,10 +1,18 @@
 module.exports = (() => {
  let env = process.env.NODE_ENV || 'development'


[💡 maintainability]
Consider using const instead of let for env since its value is not reassigned after initialization. This can prevent accidental reassignment and improve code clarity.

github-actions · 2025-11-02T05:39:17Z

config/constants/index.js

  }

+  // Support explicit local environment (mirrors platform-ui local setup)
+  const hostEnv = process.env.HOST_ENV


[💡 maintainability]
Consider using const instead of let for hostEnv since its value is not reassigned after initialization. This can prevent accidental reassignment and improve code clarity.

github-actions · 2025-11-02T05:39:21Z

config/constants/local.js

+const API_V5 = `${DEV_API_HOSTNAME}/v5`
+
+// Local service endpoints mirror platform-ui local.env.ts overrides
+const LOCAL_CHALLENGE_API = 'http://localhost:3000/v6'


[⚠️ security]
Consider using https instead of http for local service endpoints to ensure encrypted communication, even in local development environments.

github-actions · 2025-11-02T05:39:21Z

config/constants/local.js

+  CP_TRACK_ID: '9d6e0de8-df14-4c76-ba0a-a9a8cb03a4ea',
+  CHALLENGE_TYPE_ID: '927abff4-7af9-4145-8ba1-577c16e64e2e',
+  MARATHON_TYPE_ID: '929bc408-9cf2-4b3e-ba71-adfbf693046c',
+  SEGMENT_API_KEY: 'QBtLgV8vCiuRX1lDikbMjcoe9aCHkF6n',


[❗❗ security]
The SEGMENT_API_KEY is hardcoded in the file. Consider using environment variables to store sensitive information like API keys to avoid exposing them in the codebase.

github-actions · 2025-11-02T05:39:25Z

config/constants/production.js

-  SUBMISSIONS_API_URL: `${PROD_API_HOSTNAME}/v5/submissions`,
+  SUBMISSIONS_API_URL: `${PROD_API_HOSTNAME}/v6/submissions`,
  REVIEW_TYPE_API_URL: `${PROD_API_HOSTNAME}/v5/reviewTypes`,
+  REVIEWS_API_URL: `${PROD_API_HOSTNAME}/v5/reviews`, //update to use v6


[❗❗ correctness]
The comment //update to use v6 suggests an intention to update REVIEWS_API_URL to use version 6, but the URL is still pointing to v5. Ensure the URL is updated to ${PROD_API_HOSTNAME}/v6/reviews if the API version change is intended.

github-actions · 2025-11-02T05:39:25Z

config/constants/production.js

+  SUBMISSIONS_API_URL: `${PROD_API_HOSTNAME}/v6/submissions`,
  REVIEW_TYPE_API_URL: `${PROD_API_HOSTNAME}/v5/reviewTypes`,
+  REVIEWS_API_URL: `${PROD_API_HOSTNAME}/v5/reviews`, //update to use v6
+  SCORECARDS_API_URL: `${PROD_API_HOSTNAME}/v5/scorecards`, // update to use v6


[❗❗ correctness]
The comment // update to use v6 indicates an intention to update SCORECARDS_API_URL to version 6, but the URL remains at v5. Verify and update the URL to ${PROD_API_HOSTNAME}/v6/scorecards if the change is required.

github-actions · 2025-11-02T05:39:25Z

config/constants/production.js

  REVIEW_TYPE_API_URL: `${PROD_API_HOSTNAME}/v5/reviewTypes`,
+  REVIEWS_API_URL: `${PROD_API_HOSTNAME}/v5/reviews`, //update to use v6
+  SCORECARDS_API_URL: `${PROD_API_HOSTNAME}/v5/scorecards`, // update to use v6
+  WORKFLOWS_API_URL: `${PROD_API_HOSTNAME}/v5/workflows`, // update to use v6


[❗❗ correctness]
The comment // update to use v6 suggests WORKFLOWS_API_URL should be updated to v6, but it still points to v5. Confirm and update the URL to ${PROD_API_HOSTNAME}/v6/workflows if necessary.

github-actions · 2025-11-02T05:39:31Z

config/webpack.config.js

      // Add /* filename */ comments to generated require()s in the output.
      pathinfo: isEnvDevelopment,
+      // Ensure compatible hashing algorithm on modern Node versions
+      hashFunction: 'xxhash64',


[⚠️ performance]
The change to use xxhash64 for hashFunction is beneficial for performance, but ensure compatibility across environments where the build will be deployed.

github-actions · 2025-11-02T05:39:31Z

config/webpack.config.js

      minimizer: [
        // This is only used in production mode
        new TerserPlugin({
+          parallel: true,


[⚠️ performance]
Enabling parallel for TerserPlugin is a good performance improvement, but verify that it doesn't cause issues in environments with limited CPU resources.

github-actions · 2025-11-02T05:39:32Z

config/webpack.config.js

        // This is only used in production mode
        new TerserPlugin({
+          parallel: true,
+          extractComments: false,


[❗❗ correctness]
Disabling extractComments in TerserPlugin may affect legal compliance if the build includes third-party code with required license comments. Ensure this is acceptable for your use case.

github-actions · 2025-11-02T05:39:33Z

config/webpack.config.js

            inject: true,
-            template: paths.appHtml
+            // Use raw template content to avoid child compilation issues
+            templateContent: fs.readFileSync(paths.appHtml, 'utf8')


[❗❗ correctness]
Switching to templateContent for HtmlWebpackPlugin may lead to issues if the HTML template contains dynamic content or requires processing. Ensure this change doesn't affect the expected output.

github-actions · 2025-11-02T05:39:33Z

config/webpack.config.js

-      }),
+      // Merge our app constants with the standard env variables into a single DefinePlugin
+      (() => {
+        const envMap = env.stringified && env.stringified['process.env']


[⚠️ maintainability]
The merging of environment variables and constants into a single DefinePlugin instance is a good approach for maintainability, but ensure that there are no conflicts between the keys in envMap and constMap.

github-actions · 2025-11-02T05:39:33Z

config/webpack.config.js

          chunkFilename: 'static/css/[name].[contenthash:8].chunk.css'
        }),
+      // Polyfill select Node core modules for browser bundles (Webpack 5)
+      new NodePolyfillPlugin(),


[⚠️ performance]
Adding NodePolyfillPlugin is necessary for Webpack 5, but verify that it doesn't introduce unnecessary polyfills that could increase bundle size.

github-actions · 2025-11-02T05:39:33Z

config/webpack.config.js

-    performance: false
+    performance: false,
+    // When debugging, surface more internal logs from webpack itself
+    infrastructureLogging: WM_DEBUG ? { level: 'verbose' } : { level: 'warn' }


[💡 maintainability]
The use of WM_DEBUG for infrastructureLogging is a useful debugging feature, but ensure it's properly documented so developers know how to enable verbose logging.

github-actions · 2025-11-02T05:39:37Z

config/webpackDevServer.config.js


 const protocol = process.env.HTTPS === 'true' ? 'https' : 'http'
 const host = process.env.HOST || '0.0.0.0'
+const WM_DEBUG = /^(1|true|on|yes)$/i.test(String(process.env.WM_DEBUG || ''))


[⚠️ correctness]
The regular expression used to parse WM_DEBUG environment variable is case-insensitive and checks for multiple truthy values. Ensure this aligns with the intended use case, as it may lead to unexpected behavior if the environment variable is set to a non-standard truthy value.

github-actions · 2025-11-02T05:39:37Z

config/webpackDevServer.config.js

+      }
+      // Add /health endpoint in dev to mirror production server.js
+      try {
+        const healthCheck = require('topcoder-healthcheck-dropin')


[⚠️ maintainability]
The require statement for topcoder-healthcheck-dropin is inside a try block. If this module is not installed, it will fail silently unless WM_DEBUG is enabled. Consider handling this more explicitly to avoid missing the health check functionality in development.

github-actions · 2025-11-02T05:39:42Z

dev-start.sh

+# Try to fetch the JSON from S3; fall back to local file if AWS CLI is missing or S3 copy fails
+JSON_CONTENT=""
+if command -v aws >/dev/null 2>&1; then
+  if JSON_CONTENT=$(aws s3 cp "${APPVAR_S3_URI}" - 2>/dev/null); then


[⚠️ correctness]
The use of aws s3 cp without specifying a region or profile might lead to unexpected behavior if the default AWS configuration is not set correctly. Consider explicitly setting the region and profile if applicable.

github-actions · 2025-11-02T05:39:42Z

dev-start.sh

+
+if command -v nvm >/dev/null 2>&1; then
+  echo "[work-manager] Using Node via nvm..."
+  nvm use


[⚠️ correctness]
The command nvm use without specifying a version can lead to using an unintended Node.js version if multiple versions are installed. Consider specifying a version to ensure consistency.

github-actions · 2025-11-02T05:39:42Z

dev-start.sh

+      -n "${PROXY_HOST}" \
+      -s "${PROXY_SOURCE_PORT}" \
+      -t "${PROXY_TARGET_PORT}" \
+      >"${PROXY_LOG_FILE}" 2>&1 & echo $! > "${PROXY_PID_FILE}" )


[⚠️ correctness]
The background process for local-ssl-proxy is started without checking if it starts successfully. Consider adding a check to ensure the proxy starts correctly and handle any errors.

github-actions · 2025-11-02T05:39:42Z

dev-start.sh

+fi
+
+echo "[work-manager] Starting app: ${RUNNER} run start:dev (PORT=${PORT})"
+"${RUNNER}" run start:dev


[⚠️ correctness]
The command ${RUNNER} run start:dev assumes that the start:dev script is defined in the package.json. Ensure that this script exists to prevent runtime errors.

github-actions · 2025-11-02T05:39:46Z

docker/Dockerfile

-# Use the base image with Node.js
-FROM node:12
+# Use Node.js 22 base image
+FROM node:22


[❗❗ correctness]
The change from Node.js version 12 to 22 is significant. Ensure that all dependencies and the application itself are compatible with Node.js 22, as there may be breaking changes between these major versions.

github-actions · 2025-11-02T05:39:46Z

docker/Dockerfile

 RUN chown -R appuser:appuser /challenge-engine-ui
+
+# Enable corepack and prepare pnpm for installs (run as root)
+RUN corepack enable && corepack prepare pnpm@9.12.0 --activate


[⚠️ correctness]
The command corepack prepare pnpm@9.12.0 --activate is used to activate a specific version of pnpm. Verify that this version is compatible with your project dependencies and that no breaking changes have been introduced.

github-actions · 2025-11-02T05:39:46Z

docker/Dockerfile

 RUN echo "BABEL ENV in Docker: $BABEL_ENV"
-RUN npm install
-RUN npm run lint
+RUN pnpm install


[⚠️ correctness]
Switching from npm install to pnpm install can lead to differences in how dependencies are resolved and installed. Ensure that the project dependencies are correctly handled by pnpm, especially if there are any specific npm scripts or configurations that might not be compatible.

Gunasekar-K and others added 30 commits July 4, 2025 20:30

Config update for v6

a7c776a

Updating docker compose

ef828a5

Updating docker compose

ffdc6ef

Updating docker file for build fix

3dcb310

Fixes for challenge status

fc0e045

Merge branch 'v6' of github.com:topcoder-platform/work-manager into v6

67f2fed

Tweak for status dropdown

b8229b5

Status dropdown fix

2a4abb9

Fix for cancel challenge status

66e70f5

Point to v6 groups API

5791794

Update react lib to v6 version

299251c

More v6 changes

2f7bad2

Added reviewer section

abdc179

Passed reviewer details

114986d

Restructured the code: Moved the logic to services, actions and corre…

5f37507

…cted payment logic

Updated hostname in prod

d56a1ce

Added reviewer total to challenge total

866d9c8

Show Reviewer section on Challenge view page

ca279a8

Revert status change

5fe8b9f

Updated reviewers to reviewer

445377b

Changed onUpdateOthers to onUpdateReviewers

2cf363f

Renamed methods and props

e05594d

Fixed metadata , phase issue, ConvertDollarToInteger

9b17d61

Removed step

82aac16

Fixed minor bugs

c0799c2

Merge pull request #1673 from topcoder-platform/feat/challenge-review…

098c918

…er-v6 Feat/challenge reviewer v6

Empty commit for CI/CD

aa2c591

Fixed minor bugs

93d5eff

PM-1349 Add CA challenge details link to WM

ccb69b8

Merge branch 'develop' of github.com:topcoder-platform/work-manager i…

e6edb31

…nto v6

kkartunov and others added 15 commits October 28, 2025 10:01

Merge pull request #1694 from topcoder-platform/v6

779b85b

V6 -> develop

ci clean up

26a5672

-v6 clean up

ca1679c

fix: show respective scorecard types for respective review type

3323a7a

Merge pull request #1698 from topcoder-platform/pm-2609

94fc1c6

fix(PM-2609): show respective scorecard types for respective review type

fix: lint

5b8e70f

Merge pull request #1699 from topcoder-platform/pm-2609_1

97d7e07

fix(PM-2609): lint error

Better matching for "Checkpoint Screening" "Iterative Review", "Check…

ddf4170

…point Review"

fix: copilot url

fd61d4c

fix: copilot url

cd918f5

fix: copilot url

6a7f36f

fix: get only active scorecards

af17216

fix: increase per page count to 200

db32357

Merge pull request #1701 from topcoder-platform/pm-2609_2

98ac8ca

fix(PM-2609): get only active scorecards

Merge pull request #1700 from topcoder-platform/pm-2640

473d443

fix(PM-2640): copilot url in WM

github-advanced-security bot found potential problems Nov 2, 2025

View reviewed changes

github-actions bot reviewed Nov 2, 2025

View reviewed changes

github-advanced-security bot found potential problems Nov 2, 2025

View reviewed changes

github-actions bot reviewed Nov 2, 2025

View reviewed changes

kkartunov merged commit eac06e0 into master Nov 2, 2025
7 of 9 checks passed

@@ -12,7 +12,7 @@
                 e.stopPropagation()
               }, [])
-              const reviewUrl = `${REVIEW_APP_URL}/active-challenges/${challenge.id}/challenge-details`
+              const reviewUrl = `${REVIEW_APP_URL}/active-challenges/${encodeURIComponent(challenge.id)}/challenge-details`
               return (
                 <div className={styles.container}>
                   {/* Always show Review link for v5 challenges using v5 ID */}

		@@ -1,10 +1,18 @@
		module.exports = (() => {
		let env = process.env.NODE_ENV \|\| 'development'

[PROD RELEASE V6] #1702

[PROD RELEASE V6] #1702

Uh oh!

Conversation

kkartunov commented Nov 2, 2025

Uh oh!

Check warning

Uh oh!

Uh oh!

Copilot Autofix

github-actions bot Nov 2, 2025

Choose a reason for hiding this comment

Uh oh!

github-actions bot Nov 2, 2025

Choose a reason for hiding this comment

Uh oh!

github-actions bot Nov 2, 2025

Choose a reason for hiding this comment

Uh oh!

github-actions bot Nov 2, 2025

Choose a reason for hiding this comment

Uh oh!

github-actions bot Nov 2, 2025

Choose a reason for hiding this comment

Uh oh!

github-actions bot Nov 2, 2025

Choose a reason for hiding this comment

Uh oh!

github-actions bot Nov 2, 2025

Choose a reason for hiding this comment

Uh oh!

github-actions bot Nov 2, 2025

Choose a reason for hiding this comment

Uh oh!

github-actions bot Nov 2, 2025

Choose a reason for hiding this comment

Uh oh!

github-actions bot Nov 2, 2025

Choose a reason for hiding this comment

Uh oh!

github-actions bot Nov 2, 2025

Choose a reason for hiding this comment

Uh oh!

github-actions bot Nov 2, 2025

Choose a reason for hiding this comment

Uh oh!

Check notice

github-actions bot Nov 2, 2025

Choose a reason for hiding this comment

Uh oh!

github-actions bot Nov 2, 2025

Choose a reason for hiding this comment

Uh oh!

github-actions bot Nov 2, 2025

Choose a reason for hiding this comment

Uh oh!

github-actions bot Nov 2, 2025

Choose a reason for hiding this comment

Uh oh!

github-actions bot Nov 2, 2025

Choose a reason for hiding this comment

Uh oh!

github-actions bot Nov 2, 2025

Choose a reason for hiding this comment

Uh oh!

github-actions bot Nov 2, 2025

Choose a reason for hiding this comment

Uh oh!

github-actions bot Nov 2, 2025

Choose a reason for hiding this comment

Uh oh!

github-actions bot Nov 2, 2025

Choose a reason for hiding this comment

Uh oh!

github-actions bot Nov 2, 2025

Choose a reason for hiding this comment

Uh oh!

github-actions bot Nov 2, 2025

Choose a reason for hiding this comment

Uh oh!