odo - Developer-focused CLI for fast & iterative container-based application development on Podman and Kubernetes. Implementation of the open Devfile standard.
This seems due to a change in the staging Devfile registry.
Related to #6138
[FAILED] user-guides/quickstart/docs-mdx/go/go_odo_init_output.mdx
Expected
<string>: Â Â strings.Join({
  ... // 361 identical bytes
  "ent directory odo detected\nSupported architectures: all\nLanguage",
  ": Go\nProject type: Go\nApplication ports: 8080\nThe devfile \"go:1.",
-Â "0.2",
+Â "2.0",
  `" from the registry "DefaultDevfileRegistry" will be downloaded.`,
  "\n? Is this correct? Yes\n✓ Downloading devfile \"go:1.",
-Â "0.2",
+Â "2.0",
  "\" from registry \"DefaultDevfileRegistry\" [1s]\n↪ Container Conf",
  "iguration \"runtime\":\nOPEN PORTS:\n- 8080\n",
+Â "- 5858\n",
  "ENVIRONMENT VARIABLES:",
+Â "\n- DEBUG_PORT = 5858",
  "\n? Select container for which you want to change configuration? ",
  "NONE - configuration is correct\n? Enter component name: my-go-ap",
  "p\nYou can automate this command by executing:\nodo init --name my",
  "-go-app --devfile go --devfile-registry DefaultDevfileRegistry -",
  "-devfile-version 1.",
-Â "0.2",
+Â "2.0",
  "\nYour new component 'my-go-app' is ready in the current director",
  "y.\nTo start editing your component, use 'odo dev' and open this ",
  ... // 84 identical bytes
  }, "")
to be empty
In [It] at: /go/odo_1/tests/documentation/user-guides/doc_user_guides_quickstart_test.go:141 @ 11/17/23 23:24:44.57
------------------------------
/area testing /kind bug
This seems due to a change in the staging Devfile registry.
Related to #6138
https://s3.eu-de.cloud-object-storage.appdomain.cloud/odo-tests-openshift-logs/pr-7149-kubernetes-docs-tests-1230.txt