Skip to main content

Deploy details

Deploy successful for jovial-pasteur-581b4a

Bump postcss from 8.5.2 to 8.5.3

PR #761: dependabot/npm_and_yarn/postcss-8.5.3@8342ff4

Deploy summary

  • info

    Built using the Next.js Runtime

    Netlify auto-detected Next.js and used the Next.js Runtime to build and deploy your site. Learn more about deploying with Next.js on Netlify

  • info

    2 plugins ran successfully

    Select for details.

    • netlify-plugin-cache-nextjs
    • @netlify/plugin-sitemap
  • info

    Build time: 1m 28s. Total deploy time: 1m 29s

    Build started at 7:39:13 PM and ended at 7:40:41 PM. Learn more about build minutes

Deploy log

Initializing

Complete
7:38:56 PM: Build ready to start
7:39:13 PM: build-image version: e2302d7bf4e0ce66ded1ed62fd22903c51eee112 (focal)
7:39:13 PM: buildbot version: e2302d7bf4e0ce66ded1ed62fd22903c51eee112
7:39:13 PM: Fetching cached dependencies
7:39:13 PM: Starting to download cache of 956.8MB
7:39:15 PM: Finished downloading cache in 2.036s
7:39:15 PM: Starting to extract cache
7:39:21 PM: Finished extracting cache in 5.909s
7:39:21 PM: Finished fetching cache in 8.051s
7:39:21 PM: Starting to prepare the repo for build
7:39:21 PM: Preparing Git Reference pull/761/head
7:39:23 PM: Custom build command detected. Proceeding with the specified command: 'npm run ofp; npm run thp; npm run gmp; npm run build'
7:39:23 PM: Starting to install dependencies
7:39:23 PM: Started restoring cached mise cache
7:39:24 PM: Finished restoring cached mise cache
7:39:24 PM: mise python@3.13.2 install
7:39:24 PM: mise python@3.13.2 download cpython-3.13.2+20250212-x86_64-unknown-linux-gnu-install_only_stripped.tar.gz
7:39:25 PM: mise python@3.13.2 extract cpython-3.13.2+20250212-x86_64-unknown-linux-gnu-install_only_stripped.tar.gz
7:39:25 PM: mise python@3.13.2 python --version
7:39:25 PM: mise python@3.13.2 Python 3.13.2
7:39:25 PM: mise python@3.13.2 installed
7:39:25 PM: Python version set to 3.13
7:39:26 PM: Collecting pipenv
7:39:26 PM: Downloading pipenv-2024.4.1-py3-none-any.whl.metadata (17 kB)
7:39:26 PM: Collecting certifi (from pipenv)
7:39:26 PM: Downloading certifi-2025.1.31-py3-none-any.whl.metadata (2.5 kB)
7:39:26 PM: Collecting packaging>=22 (from pipenv)
7:39:26 PM: Downloading packaging-24.2-py3-none-any.whl.metadata (3.2 kB)
7:39:26 PM: Collecting setuptools>=67 (from pipenv)
7:39:26 PM: Downloading setuptools-75.8.0-py3-none-any.whl.metadata (6.7 kB)
7:39:26 PM: Collecting virtualenv>=20.24.2 (from pipenv)
7:39:26 PM: Downloading virtualenv-20.29.2-py3-none-any.whl.metadata (4.5 kB)
7:39:27 PM: Collecting distlib<1,>=0.3.7 (from virtualenv>=20.24.2->pipenv)
7:39:27 PM: Downloading distlib-0.3.9-py2.py3-none-any.whl.metadata (5.2 kB)
7:39:27 PM: Collecting filelock<4,>=3.12.2 (from virtualenv>=20.24.2->pipenv)
7:39:27 PM: Downloading filelock-3.17.0-py3-none-any.whl.metadata (2.9 kB)
7:39:27 PM: Collecting platformdirs<5,>=3.9.1 (from virtualenv>=20.24.2->pipenv)
7:39:27 PM: Downloading platformdirs-4.3.6-py3-none-any.whl.metadata (11 kB)
7:39:27 PM: Downloading pipenv-2024.4.1-py3-none-any.whl (3.0 MB)
7:39:27 PM: ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 3.0/3.0 MB 77.6 MB/s eta 0:00:00
7:39:27 PM: Downloading packaging-24.2-py3-none-any.whl (65 kB)
7:39:27 PM: Downloading setuptools-75.8.0-py3-none-any.whl (1.2 MB)
7:39:27 PM: ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 1.2/1.2 MB 95.8 MB/s eta 0:00:00
7:39:27 PM: Downloading virtualenv-20.29.2-py3-none-any.whl (4.3 MB)
7:39:27 PM: ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 4.3/4.3 MB 203.4 MB/s eta 0:00:00
7:39:27 PM: Downloading certifi-2025.1.31-py3-none-any.whl (166 kB)
7:39:27 PM: Downloading distlib-0.3.9-py2.py3-none-any.whl (468 kB)
7:39:27 PM: Downloading filelock-3.17.0-py3-none-any.whl (16 kB)
7:39:27 PM: Downloading platformdirs-4.3.6-py3-none-any.whl (18 kB)
7:39:27 PM: Installing collected packages: distlib, setuptools, platformdirs, packaging, filelock, certifi, virtualenv, pipenv
7:39:29 PM: Successfully installed certifi-2025.1.31 distlib-0.3.9 filelock-3.17.0 packaging-24.2 pipenv-2024.4.1 platformdirs-4.3.6 setuptools-75.8.0 virtualenv-20.29.2
7:39:29 PM: [notice] A new release of pip is available: 24.3.1 -> 25.0.1
7:39:29 PM: [notice] To update, run: pip install --upgrade pip
7:39:29 PM: Attempting Ruby version 2.7.1, read from environment
7:39:29 PM: Started restoring cached Ruby version
7:39:29 PM: Finished restoring cached Ruby version
7:39:30 PM: Using Ruby version 2.7.1
7:39:30 PM: Started restoring cached go cache
7:39:30 PM: Finished restoring cached go cache
7:39:30 PM: Installing Go version 1.14.4 (requested 1.14.4)
7:39:34 PM: go version go1.14.4 linux/amd64
7:39:35 PM: Using PHP version 8.0
7:39:36 PM: Started restoring cached Node.js version
7:39:37 PM: Finished restoring cached Node.js version
7:39:37 PM: Attempting Node.js version 'lts/iron' from .nvmrc
7:39:38 PM: v20.18.3 is already installed.
7:39:38 PM: Now using node v20.18.3 (npm v10.8.2)
7:39:38 PM: Enabling Node.js Corepack
7:39:38 PM: Started restoring cached build plugins
7:39:38 PM: Finished restoring cached build plugins
7:39:38 PM: Started restoring cached corepack dependencies
7:39:38 PM: Finished restoring cached corepack dependencies
7:39:38 PM: No npm workspaces detected
7:39:38 PM: Started restoring cached node modules
7:39:38 PM: Finished restoring cached node modules
7:39:38 PM: Installing npm packages using npm version 10.8.2
7:39:39 PM: changed 1 package, and audited 775 packages in 801ms
7:39:39 PM: 174 packages are looking for funding
7:39:39 PM: run `npm fund` for details
7:39:39 PM: found 0 vulnerabilities
7:39:39 PM: npm packages installed
7:39:39 PM: Successfully installed dependencies
7:39:39 PM: Starting build script
7:39:41 PM: Detected 1 framework(s)
7:39:41 PM: "next" at version "15.1.7"
7:39:41 PM: Section completed: initializing

Building

Complete
7:39:42 PM: Netlify Build
7:39:42 PM: ────────────────────────────────────────────────────────────────
7:39:42 PM:
7:39:42 PM: ❯ Version
7:39:42 PM: @netlify/build 29.59.1
7:39:42 PM:
7:39:42 PM: ❯ Flags
7:39:42 PM: accountId: 5f75eccd8af0700090155c32
7:39:42 PM: baseRelDir: true
7:39:42 PM: buildId: 67bccad0499cd40008611aec
7:39:42 PM: deployId: 67bccad0499cd40008611aee
7:39:42 PM:
7:39:42 PM: ❯ Current directory
7:39:42 PM: /opt/build/repo
7:39:42 PM:
7:39:42 PM: ❯ Config file
7:39:42 PM: /opt/build/repo/netlify.toml
7:39:42 PM:
7:39:42 PM: ❯ Context
7:39:42 PM: deploy-preview
7:39:42 PM:
7:39:42 PM: ❯ Using Next.js Runtime - v5.9.4
7:39:42 PM:
7:39:42 PM: ❯ Loading plugins
7:39:42 PM: - @netlify/plugin-sitemap@0.8.1 from Netlify app
7:39:42 PM: - netlify-plugin-cache-nextjs@1.4.0 from Netlify app
7:39:43 PM: Next.js cache restored
7:39:44 PM: Restored the cached .next folder at the location `.next/cache`
7:39:44 PM:
7:39:44 PM: build.command from netlify.toml
7:39:44 PM: ────────────────────────────────────────────────────────────────
7:39:44 PM: ​
7:39:44 PM: $ npm run ofp; npm run thp; npm run gmp; npm run build
7:39:44 PM: > acm-website@0.1.0 ofp
7:39:44 PM: > node scripts/officer-parser.mjs
7:39:45 PM: Output successfully saved to offoutput.json
7:39:45 PM: > acm-website@0.1.0 thp
7:39:45 PM: > node scripts/town-hall-generator.mjs
7:39:46 PM: Output successfully saved to townhall.json
7:39:47 PM: Output successfully saved to past-townhall.json
7:39:47 PM: > acm-website@0.1.0 gmp
7:39:47 PM: > node scripts/gm-generator.mjs
7:39:48 PM: Saved output: gmData.json
7:39:48 PM: > acm-website@0.1.0 build
7:39:48 PM: > npm run ofp && npm run thp && npm run gmp && next build
7:39:48 PM: > acm-website@0.1.0 ofp
7:39:48 PM: > node scripts/officer-parser.mjs
7:39:49 PM: Output successfully saved to offoutput.json
7:39:49 PM: > acm-website@0.1.0 thp
7:39:49 PM: > node scripts/town-hall-generator.mjs
7:39:50 PM: Output successfully saved to townhall.json
7:39:51 PM: Output successfully saved to past-townhall.json
7:39:51 PM: > acm-website@0.1.0 gmp
7:39:51 PM: > node scripts/gm-generator.mjs
7:39:52 PM: Saved output: gmData.json
7:39:52 PM: ▲ Next.js 15.1.7
7:39:52 PM: Linting and checking validity of types ...
7:39:53 PM: ./pages/gm/f21.js
7:39:53 PM: 218:15 Warning: Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element
7:39:53 PM: 226:15 Warning: Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element
7:39:53 PM: 231:15 Warning: Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element
7:39:53 PM: 239:15 Warning: Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element
7:39:53 PM: 247:15 Warning: Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element
7:39:53 PM: 255:15 Warning: Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element
7:39:53 PM: 260:15 Warning: Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element
7:39:53 PM: 265:15 Warning: Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element
7:39:53 PM: 279:15 Warning: Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element
7:39:53 PM: 287:15 Warning: Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element
7:39:53 PM: ./pages/gm/w22.js
7:39:53 PM: 218:15 Warning: Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element
7:39:53 PM: 226:15 Warning: Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element
7:39:53 PM: 231:15 Warning: Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element
7:39:53 PM: 239:15 Warning: Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element
7:39:53 PM: 247:15 Warning: Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element
7:39:53 PM: 255:15 Warning: Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element
7:39:53 PM: 260:15 Warning: Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element
7:39:53 PM: 265:15 Warning: Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element
7:39:53 PM: 279:15 Warning: Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element
7:39:53 PM: 287:15 Warning: Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element
7:39:53 PM: ./components/Footer.js
7:39:53 PM: 119:27 Warning: Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element
7:39:53 PM: info - Need to disable some ESLint rules? Learn more here: https://nextjs.org/docs/app/api-reference/config/eslint#disabling-rules
7:39:53 PM: Creating an optimized production build ...
7:39:54 PM: Disabled SWC as replacement for Babel because of custom Babel configuration ".babelrc" https://nextjs.org/docs/messages/swc-disabled
7:39:54 PM: Using external babel configuration from /opt/build/repo/.babelrc
7:39:54 PM: It looks like there is a custom Babel configuration that can be removed.
7:39:58 PM: Disabled SWC as replacement for Babel because of custom Babel configuration ".babelrc" https://nextjs.org/docs/messages/swc-disabled
7:39:59 PM: Disabled SWC as replacement for Babel because of custom Babel configuration ".babelrc" https://nextjs.org/docs/messages/swc-disabled
7:39:59 PM: Using external babel configuration from /opt/build/repo/.babelrc
7:39:59 PM: It looks like there is a custom Babel configuration that can be removed.
7:40:04 PM: Compiled successfully
7:40:04 PM: Collecting page data ...
7:40:07 PM: Generating static pages (0/24) ...
7:40:07 PM: Generating static pages (6/24)
7:40:07 PM: Generating static pages (12/24)
7:40:08 PM: Generating static pages (18/24)
7:40:10 PM: Warning: Invalid Image URL: TypeError: Invalid URL
7:40:10 PM: Warning: Invalid Image URL: TypeError: Invalid URL
7:40:10 PM: Warning: Invalid Image URL: TypeError: Invalid URL
7:40:10 PM: Warning: Invalid Image URL: TypeError: Invalid URL
7:40:10 PM: Warning: Invalid Image URL: TypeError: Invalid URL
7:40:10 PM: Warning: Invalid Image URL: TypeError: Invalid URL
7:40:10 PM: Warning: Invalid Image URL: TypeError: Invalid URL
7:40:10 PM: Generating static pages (24/24)
7:40:18 PM: Finalizing page optimization ...
7:40:18 PM: Collecting build traces ...
7:40:26 PM: Route (pages) Size First Load JS
7:40:26 PM: ┌ ○ / 1.88 kB 136 kB
7:40:26 PM: ├ /_app 0 B 97.1 kB
7:40:26 PM: ├ ○ /404 1.23 kB 98.3 kB
7:40:26 PM: ├ ○ /about 5.19 kB 143 kB
7:40:26 PM: ├ └ css/45a39d4b794d26b4.css 1.5 kB
7:40:26 PM: ├ ○ /committees 2.26 kB 138 kB
7:40:26 PM: ├ ○ /covid 1.63 kB 123 kB
7:40:26 PM: ├ ○ /dev (503 ms) 8.51 kB 146 kB
7:40:26 PM: ├ └ css/53366f091a089070.css 1.87 kB
7:40:26 PM: ├ ● /events (ISR: 3600 Seconds) (1893 ms) 123 kB 244 kB
7:40:26 PM: ├ └ css/fd0a213c1c86cc1e.css 3.44 kB
7:40:26 PM: ├ ○ /gm 3.92 kB 132 kB
7:40:26 PM: ├ ○ /gm/f21 (503 ms) 2.49 kB 126 kB
7:40:26 PM: ├ ○ /gm/f22 3.24 kB 131 kB
7:40:26 PM: ├ ○ /gm/f23 3.19 kB 131 kB
7:40:26 PM: ├ ○ /gm/w22 2.29 kB 126 kB
7:40:26 PM: ├ ○ /gm/w23 3.26 kB 131 kB
7:40:26 PM: ├ ○ /gm/w24 3.2 kB 131 kB
7:40:26 PM: ├ ○ /impact 6.06 kB 144 kB
7:40:26 PM: ├ └ css/e87a2b3dcb87ea63.css 1.68 kB
7:40:26 PM: ├ ○ /internship 6.18 kB 140 kB
7:40:26 PM: ├ └ css/a789e5593fa10f7f.css 1.73 kB
7:40:26 PM: ├ ○ /jedi 7.67 kB 132 kB
7:40:26 PM: ├ └ css/200e21a281656731.css 811 B
7:40:26 PM: ├ ○ /jedi/allyship 6.61 kB 131 kB
7:40:26 PM: ├ └ css/a9eda44ce8fcabc7.css 812 B
7:40:26 PM: ├ ○ /jedi/meet (503 ms) 7.35 kB 133 kB
7:40:26 PM: ├ └ css/aade7765771753d6.css 1.43 kB
7:40:26 PM: ├ ○ /officers 2.46 kB 150 kB
7:40:26 PM: ├ └ css/4b821495f985bc93.css 1.31 kB
7:40:26 PM: ├ ○ /sponsors (503 ms) 1.51 kB 136 kB
7:40:26 PM: ├ ○ /techgala 1.11 kB 135 kB
7:40:26 PM: └ ○ /town-hall (503 ms) 5.37 kB 131 kB
7:40:26 PM: + First Load JS shared by all 104 kB
7:40:26 PM: ├ chunks/framework-b96261d959dd50e7.js 44.8 kB
7:40:26 PM: ├ chunks/main-ead5690ae0af8f2d.js 32.1 kB
7:40:26 PM: ├ chunks/pages/_app-8966bc1f29819a34.js 18.4 kB
7:40:26 PM: └ other shared chunks (total) 9.04 kB
7:40:26 PM: ○ (Static) prerendered as static content
7:40:26 PM: ● (SSG) prerendered as static HTML (uses getStaticProps)
7:40:26 PM: (ISR) incremental static regeneration (uses revalidate in getStaticProps)
7:40:26 PM: ​
7:40:26 PM: (build.command completed in 42s)
7:40:26 PM: Next.js cache saved
7:40:26 PM: Next.js cache saved
7:40:27 PM:
7:40:27 PM: Functions bundling
7:40:27 PM: ────────────────────────────────────────────────────────────────
7:40:27 PM: ​
7:40:27 PM: Packaging Functions from .netlify/functions-internal directory:
7:40:27 PM: - ___netlify-server-handler/___netlify-server-handler.mjs
7:40:27 PM: ​
7:40:29 PM: ​
7:40:29 PM: (Functions bundling completed in 2.5s)
7:40:30 PM: Creating sitemap from files...
7:40:30 PM: Sitemap Built! sitemap.xml
7:40:30 PM: (node:5762) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 unpipe listeners added to [Socket]. Use emitter.setMaxListeners() to increase limit
7:40:30 PM: (Use `node --trace-warnings ...` to show where the warning was created)
7:40:30 PM: (node:5762) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 error listeners added to [Socket]. Use emitter.setMaxListeners() to increase limit
7:40:30 PM: (node:5762) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 close listeners added to [Socket]. Use emitter.setMaxListeners() to increase limit
7:40:30 PM: (node:5762) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 finish listeners added to [Socket]. Use emitter.setMaxListeners() to increase limit
7:40:30 PM: (node:5762) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 unpipe listeners added to [Socket]. Use emitter.setMaxListeners() to increase limit
7:40:30 PM: (node:5762) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 error listeners added to [Socket]. Use emitter.setMaxListeners() to increase limit
7:40:30 PM: (node:5762) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 close listeners added to [Socket]. Use emitter.setMaxListeners() to increase limit
7:40:30 PM: (node:5762) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 finish listeners added to [Socket]. Use emitter.setMaxListeners() to increase limit
7:40:30 PM: No .next folder at the location `.next/cache`
7:40:30 PM:
7:40:46 PM: (Netlify Build completed in 1m 4.4s)
7:40:48 PM: Section completed: building
7:41:03 PM: Finished processing build request in 1m50.574s

Deploying

Complete
7:40:30 PM: Deploy site
7:40:30 PM: ────────────────────────────────────────────────────────────────
7:40:30 PM: ​
7:40:30 PM: Starting to deploy site from '.next'
7:40:31 PM: Calculating files to upload
7:40:33 PM: 3 new file(s) to upload
7:40:33 PM: 1 new function(s) to upload
7:40:41 PM: Section completed: deploying
7:40:43 PM: Finished waiting for live deploy in 2.143s
7:40:43 PM: Site deploy was successfully initiated
7:40:43 PM: ​
7:40:43 PM: (Deploy site completed in 13s)

Cleanup

Complete
7:40:46 PM: Netlify Build Complete
7:40:46 PM: ────────────────────────────────────────────────────────────────
7:40:46 PM: ​
7:40:47 PM: Caching artifacts
7:40:47 PM: Started saving node modules
7:40:47 PM: Finished saving node modules
7:40:47 PM: Started saving build plugins
7:40:47 PM: Finished saving build plugins
7:40:47 PM: Started saving mise cache
7:40:47 PM: Finished saving mise cache
7:40:47 PM: Started saving corepack cache
7:40:47 PM: Finished saving corepack cache
7:40:47 PM: Started saving pip cache
7:40:47 PM: Finished saving pip cache
7:40:47 PM: Started saving emacs cask dependencies
7:40:47 PM: Finished saving emacs cask dependencies
7:40:47 PM: Started saving maven dependencies
7:40:47 PM: Finished saving maven dependencies
7:40:47 PM: Started saving boot dependencies
7:40:47 PM: Finished saving boot dependencies
7:40:47 PM: Started saving rust rustup cache
7:40:47 PM: Finished saving rust rustup cache
7:40:47 PM: Started saving go dependencies
7:40:47 PM: Finished saving go dependencies
7:40:48 PM: Build script success
7:41:01 PM: Uploading Cache of size 935.7MB
7:41:03 PM: Section completed: cleanup

Post-processing

Complete
7:40:41 PM: Skipping form detection
7:40:41 PM: Post processing done
7:40:41 PM: Section completed: postprocessing
7:40:41 PM: Post processing - redirect rules
7:40:41 PM: Starting post processing
7:40:41 PM: Post processing - header rules
7:40:43 PM: Site is live ✨