Go version 1.13?

When I build my functions in Netlify, go version reports go version go1.12 linux/amd64. Is there any way to use Go 1.13? My laptop has 1.13, and I keep running into small incompatibilities, such as new standard library methods, only available in 1.13.

I think this shows that we’ll accept a $GIMME_GO_VERSION:

I don’t know anyone else who’s tried to change that so not sure if it works, but hopefully you’ll let us know what you discover here :slight_smile:

No effect, sadly. Still reports

8:00:21 PM: + go version
8:00:21 PM: go version go1.12 linux/amd64

Here is the whole log:

7:59:50 PM: Build ready to start
7:59:53 PM: build-image version: 9cade8af58c2cf3a17a1e9433d2e979149488837
7:59:53 PM: build-image tag: v3.3.5
7:59:53 PM: buildbot version: eb060c4dc3a8a73f9004f460f04632708166ca51
7:59:53 PM: Fetching cached dependencies
7:59:53 PM: Starting to download cache of 269.8MB
7:59:55 PM: Finished downloading cache in 1.659097094s
7:59:55 PM: Starting to extract cache
8:00:05 PM: Finished extracting cache in 10.346727983s
8:00:05 PM: Finished fetching cache in 12.235170155s
8:00:05 PM: Starting to prepare the repo for build
8:00:06 PM: Preparing Git Reference refs/heads/master
8:00:07 PM: Found Netlify configuration file. Overriding site configuration
8:00:07 PM: Different functions path detected, going to use the one specified in the Netlify configuration file: ‘functions’ versus ‘’ in the Netlify UI
8:00:07 PM: Creating functions prep folder
8:00:07 PM: Starting build script
8:00:07 PM: Installing dependencies
8:00:08 PM: Started restoring cached node version
8:00:10 PM: Finished restoring cached node version
8:00:11 PM: v12.13.1 is already installed.
8:00:12 PM: Now using node v12.13.1 (npm v6.12.1)
8:00:12 PM: Attempting ruby version 2.6.2, read from environment
8:00:14 PM: Using ruby version 2.6.2
8:00:14 PM: Using PHP version 5.6
8:00:14 PM: Started restoring cached node modules
8:00:14 PM: Finished restoring cached node modules
8:00:14 PM: Started restoring cached yarn cache
8:00:14 PM: Finished restoring cached yarn cache
8:00:15 PM: Installing NPM modules using Yarn version 1.17.0
8:00:17 PM:
8:00:17 PM:
8:00:17 PM: yarn install v1.17.0
8:00:17 PM:
8:00:17 PM:
8:00:17 PM: [1/4] Resolving packages…
8:00:18 PM:
8:00:18 PM: success Already up-to-date.
8:00:18 PM:
8:00:18 PM:
8:00:18 PM: Done in 1.34s.
8:00:18 PM: NPM modules installed using Yarn
8:00:18 PM: Started restoring cached go cache
8:00:21 PM: Finished restoring cached go cache
8:00:21 PM: Installing Go version 1.12
8:00:21 PM: unset GOOS;
8:00:21 PM: unset GOARCH;
8:00:21 PM: export GOROOT=’/opt/buildhome/.gimme_cache/versions/go1.12.linux.amd64’;
8:00:21 PM: export PATH="/opt/buildhome/.gimme_cache/versions/go1.12.linux.amd64/bin:{PATH}"; 8:00:21 PM: go version >&2; 8:00:21 PM: export GIMME_ENV='/opt/buildhome/.gimme_cache/env/go1.12.linux.amd64.env'; 8:00:21 PM: go version go1.12 linux/amd64 8:00:21 PM: Installing missing commands 8:00:21 PM: Verify run directory 8:00:21 PM: Executing user command: ./build.sh 8:00:21 PM: +++ dirname ./build.sh 8:00:21 PM: ++ cd . 8:00:21 PM: ++ pwd 8:00:21 PM: + THIS_DIR=/opt/buildhome/.gimme_cache/gopath/src/github.com/spotlightpa/almanack 8:00:21 PM: + cd /opt/buildhome/.gimme_cache/gopath/src/github.com/spotlightpa/almanack 8:00:21 PM: + go version 8:00:21 PM: go version go1.12 linux/amd64 8:00:21 PM: + GOBIN=/opt/buildhome/.gimme_cache/gopath/src/github.com/spotlightpa/almanack/functions 8:00:21 PM: + go install ./cmd/... 8:00:23 PM: + yarn run build 8:00:23 PM: 8:00:23 PM: 8:00:23 PM: yarn run v1.17.0 8:00:23 PM: 8:00:23 PM: vue-cli-service build --modern
8:00:24 PM: - Building legacy bundle for production…
8:00:54 PM: WARNING Compiled with 3 warnings1:00:54 AM
8:00:54 PM: warning
8:00:54 PM: asset size limit: The following asset(s) exceed the recommended size limit (244 KiB).
8:00:54 PM: This can impact web performance.
8:00:54 PM: Assets:
8:00:54 PM: js/chunk-vendors-legacy.4d4a4fdb.js (350 KiB)
8:00:54 PM: warning
8:00:54 PM: entrypoint size limit: The following entrypoint(s) combined asset size exceeds the recommended limit (244 KiB). This can impact web performance.
8:00:54 PM: Entrypoints:
8:00:54 PM: app (423 KiB)
8:00:54 PM: js/chunk-vendors-legacy.4d4a4fdb.js
8:00:54 PM: css/app.6fe1146e.css
8:00:54 PM: js/app-legacy.2bdf08af.js
8:00:54 PM: warning
8:00:54 PM: webpack performance recommendations:
8:00:54 PM: You can limit the size of your bundles by using import() or require.ensure to lazy load some parts of your application.
8:00:54 PM: For more info visit https://webpack.js.org/guides/code-splitting/
8:00:54 PM: File Size Gzipped
8:00:54 PM: dist/js/chunk-vendors-legacy.4d4a4fdb. 349.75 KiB 112.18 KiB
8:00:54 PM: js
8:00:54 PM: dist/js/app-legacy.2bdf08af.js 17.47 KiB 5.67 KiB
8:00:54 PM: dist/css/app.6fe1146e.css 55.53 KiB 8.75 KiB
8:00:54 PM: Images and other types of assets omitted.
8:00:54 PM: - Building modern bundle for production…
8:01:22 PM: WARNING Compiled with 3 warnings1:01:22 AM
8:01:22 PM: warning
8:01:22 PM: asset size limit: The following asset(s) exceed the recommended size limit (244 KiB).
8:01:22 PM: This can impact web performance.
8:01:22 PM: Assets:
8:01:22 PM: js/chunk-vendors.4fc3c478.js (318 KiB)
8:01:22 PM: warning
8:01:22 PM: entrypoint size limit: The following entrypoint(s) combined asset size exceeds the recommended limit (244 KiB). This can impact web performance.
8:01:22 PM: Entrypoints:
8:01:22 PM: app (390 KiB)
8:01:22 PM: js/chunk-vendors.4fc3c478.js
8:01:22 PM: css/app.6fe1146e.css
8:01:22 PM: js/app.88007642.js
8:01:22 PM: warning
8:01:22 PM: webpack performance recommendations:
8:01:22 PM: You can limit the size of your bundles by using import() or require.ensure to lazy load some parts of your application.
8:01:22 PM: For more info visit https://webpack.js.org/guides/code-splitting/
8:01:23 PM: File Size Gzipped
8:01:23 PM: dist/js/chunk-vendors.4fc3c478.js 318.46 KiB 102.90 KiB
8:01:23 PM: dist/js/app.88007642.js 15.54 KiB 5.25 KiB
8:01:23 PM: dist/css/app.6fe1146e.css 55.53 KiB 8.75 KiB
8:01:23 PM: Images and other types of assets omitted.
8:01:23 PM: DONE Build complete. The dist directory is ready to be deployed.
8:01:23 PM: INFO Check out deployment instructions at https://cli.vuejs.org/guide/deployment.html
8:01:24 PM:
8:01:24 PM:
8:01:24 PM: Done in 60.51s.
8:01:24 PM: Function Dir: /opt/build/repo/functions
8:01:24 PM: TempDir: /tmp/zisi-5de5b386c6d507000961a849
8:01:25 PM: Prepping functions with zip-it-and-ship-it 0.3.1
8:01:25 PM: [ { path: ‘/tmp/zisi-5de5b386c6d507000961a849/almanack-api’,
8:01:25 PM: runtime: ‘go’ } ]
8:01:25 PM: Prepping functions complete
8:01:25 PM: Caching artifacts
8:01:25 PM: Started saving node modules
8:01:25 PM: Finished saving node modules
8:01:25 PM: Started saving yarn cache
8:01:25 PM: Finished saving yarn cache
8:01:25 PM: Started saving pip cache
8:01:25 PM: Finished saving pip cache
8:01:25 PM: Started saving emacs cask dependencies
8:01:25 PM: Finished saving emacs cask dependencies
8:01:25 PM: Started saving maven dependencies
8:01:25 PM: Finished saving maven dependencies
8:01:25 PM: Started saving boot dependencies
8:01:25 PM: Finished saving boot dependencies
8:01:26 PM: Started saving go dependencies
8:01:29 PM: Finished saving go dependencies
8:01:29 PM: Build script success
8:01:29 PM: Starting to deploy site from ‘dist’
8:01:29 PM: Creating deploy tree
8:01:29 PM: 1 new files to upload
8:01:29 PM: 1 new functions to upload
8:01:32 PM: Starting post processing
8:01:32 PM: Post processing done
8:01:32 PM: Site is live
8:02:22 PM: Finished processing build request in 2m28.699744083s

Okay, I have changed my build script, and I think it works now. Instead of just setting the ENV var, you have to manually kick off gimme with eval "$(gimme stable)".

Is it possible your image’s ENV has installGoVersion set somewhere, such that the GIMME_GO_VERSION gets overwritten? My guess is that something like that is happening.

I’m glad to hear you got something working!

I’m not sure exactly what is happening here, but that variable is used:

If you think it’s not being used correctly (minus my bad advice to set $GIMME_GO_VERSION which was made from an incomplete reading of that source), mind filing an issue here?