v7.5.0-rc.33

Changelog

• Fix invisible tags in MetaTag & Metadata JSDoc (#10504) by @Philzen

  This change fixes the common pitfall that tags of all kind are not visible in JSDoc view because it will try to interpret them as HTML. Now these tags should be visible when the JSDoc is rendered. See #10504 for more information

• feat(upgrade): Use GitHub token if available when downloading patches (#10515) by @Tobbe

  If a GitHub token is available in the environment we use that when fetching the
  git tree from GitHub. That way we're less likely to be rate limited. For most
  users the token shouldn't be needed. The free allowance/usage of the GitHub API
  should be enough.

  We support GH_TOKEN, GITHUB_TOKEN and REDWOOD_GITHUB_TOKEN as the env var names

• Add redwood.toml to yarn rw info (#10518) by @Tobbe

  The project redwood.toml file is now included in the yarn rw info output to
  make it easier and faster to help with issue reports

  Before

  System:
    OS: macOS 14.1.1
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.11.0 - /usr/local/bin/node
    Yarn: 4.1.1 - /usr/local/bin/yarn
  Databases:
    SQLite: 3.39.5 - /usr/bin/sqlite3
  Browsers:
    Safari: 17.1
  

  After

  System:
    OS: macOS 14.1.1
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.11.0 - /usr/local/bin/node
    Yarn: 4.1.1 - /usr/local/bin/yarn
  Databases:
    SQLite: 3.39.5 - /usr/bin/sqlite3
  Browsers:
    Safari: 17.1
  redwood.toml:
    [web]
      title = "Redwood App"
      port = 8910
      apiUrl = "/.redwood/functions" # You can customize graphql and dbauth urls individually too: see https://redwoodjs.com/docs/app-configuration-redwood-toml#api-paths
      includeEnvironmentVariables = [
        # Add any ENV vars that should be available to the web side to this array
        # See https://redwoodjs.com/docs/environment-variables#web
      ]
    [api]
      port = 8911
    [browser]
      open = true
    [notifications]
      versionUpdates = ["latest"]
  

• feat(baremetal): Add verbose output to ssh exec (#10525) by @Tobbe

  Passing --verbose to the baremetal deploy command is supposed to give you
  more detailed info about what's happening. Previously however passing
  --verbose didn't actually provide any extra information. This PR adds logging
  to the new SshExecutor class so that you can see exactly what SSH commands are
  being run, and in what path.

  Standard output (this stays the same before and after)
  

  Before (verbose output)
  
  Doesn't really help much compared to the standard output 😅

  After (verbose output)
  

• feat(baremetal): Add more details to error messages (#10527) by @Tobbe

  Now when an ssh command execution fails the error message will additionally
  include the directory it was executed in and the full stderr message

  Before
  

  After