Skip to content

History / Modules

Revisions

  • semantic import versioning: explicitly mention including '/vN' in 'go get' commands.

    @thepudds thepudds committed Aug 30, 2019
  • Restore modules wiki page.

    @heschi heschi committed Aug 26, 2019
  • Destroyed Modules (markdown)

    @regahawlery regahawlery committed Aug 26, 2019
  • Noting that athens.azurefd.net is an experimental server

    @arschles arschles committed Aug 9, 2019
  • adjust repo name in Quick Start

    @thepudds thepudds committed Aug 9, 2019
  • adjust directory name in Quick Start

    @thepudds thepudds committed Aug 9, 2019
  • update name of binary in Quick Start section

    @thepudds thepudds committed Aug 9, 2019
  • show initializing git in the Quick Start section. The connection between repo location and module path is something people sometimes miss when ramping up on modules.

    @thepudds thepudds committed Aug 9, 2019
  • Added go-mod-outdated in Community tools

    @psampaz psampaz committed Aug 8, 2019
  • Updated Modules (markdown)

    @jasonjao jasonjao committed Jul 29, 2019
  • Format: Are there "always on" module repositories and enterprise proxies?

    @jasonjao jasonjao committed Jul 29, 2019
  • Remove extraneous word

    @zwass zwass committed Jul 13, 2019
  • add FAQ on using a go.mod to exclude large or unnecessary files from a module

    @thepudds thepudds committed Jun 17, 2019
  • Added akyoto/mgit to community tools

    @akyoto akyoto committed Jun 8, 2019
  • Add goproxy.io

    @oiooj oiooj committed Jun 6, 2019
  • Updated Modules (markdown)

    @aofei aofei committed Jun 5, 2019
  • update table of contents to point to new FAQs

    @thepudds thepudds committed Jun 3, 2019
  • add FAQ on repos that have opted in to modules without applying semver tags

    @thepudds thepudds committed Jun 2, 2019
  • mention 'go list -mod=readonly all' technique in FAQ on troubleshooting versions of a your dependency

    @thepudds thepudds committed Jun 2, 2019
  • mention GOPROXY performance benefits as an alternative to creating a multi-module repository

    @thepudds thepudds committed Jun 2, 2019
  • Minor spelling/formatting fixes

    @ian-howell ian-howell committed May 30, 2019
  • add FAQ on set of steps to resolve "parsing go.mod: unexpected module path" error caused by a mismatch between import paths vs. declared module identity

    @thepudds thepudds committed May 29, 2019
  • add section on avoiding breaking import paths in migrating to modules section

    @thepudds thepudds committed May 29, 2019
  • update FAQ on replace: mention 'go.mod' is required for file system target, and 'require' is now optional

    @thepudds thepudds committed May 24, 2019
  • Replace bullet points with paragraphs on "When should I use the replace directive?" FAQ's section

    @shuLhan shuLhan committed May 7, 2019
  • Updated Modules (markdown)

    @aofei aofei committed May 7, 2019
  • update vendoring FAQ to also mention a 'vendor' directory can provide dependencies to Go 1.11+ when module-mode is disabled

    @thepudds thepudds committed May 6, 2019
  • Updated Modules (markdown)

    @aofei aofei committed Apr 29, 2019
  • clarify prelease tag behavior and slightly reorganize 'How to Upgrade' section

    @thepudds thepudds committed Apr 11, 2019
  • Clarify that go get -u ignores pre-releases

    @mholt mholt committed Apr 11, 2019