-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove deprecated terms from config.toml #112
Remove deprecated terms from config.toml #112
Conversation
7de8c6d
to
45b89b4
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@apoorvajagtap Apologies, this somehow went under my radar. Do you have any docs that you can link with regards to this change, where for example the deprecation is explained. Also, there seems to be a build failure. Any idea what this might be caused by:
8:46:00 AM: "build.command" failed
8:46:00 AM: ────────────────────────────────────────────────────────────────
8:46:00 AM:
8:46:00 AM: Error message
8:46:00 AM: Command failed with exit code 2: make netlify-preview (https://ntl.fyi/exit-code-2)
8:46:00 AM:
8:46:00 AM: Error location
8:46:00 AM: In build.command from netlify.toml:
8:46:00 AM: make netlify-preview
8:46:00 AM:
8:46:00 AM: Resolved config
8:46:00 AM: build:
8:46:00 AM: command: make netlify-preview
8:46:00 AM: commandOrigin: config
8:46:00 AM: environment:
8:46:00 AM: - HUGO_VERSION
8:46:00 AM: - REVIEW_ID
8:46:00 AM: publish: /opt/build/repo/public
8:46:00 AM: publishOrigin: config
8:46:01 AM: Failed during stage "building site": Build script returned non-zero exit code: 2
8:46:01 AM: Build failed due to a user error: Build script returned non-zero exit code: 2
8:46:01 AM: Failing build: Failed to build site
8:46:01 AM: Finished processing build request in 2m35.385s
45b89b4
to
a3419a2
Compare
Hi @HeavyWombat linking the release notes & related issue where these changes were introduced. Also, the errors indicate that the custom params on the language top level were deprecated in Hugo v0.112.0 and will be removed in Hugo 0.125.0. So, it is expected to put the value below [languages.en.params]. See https://gohugo.io/content-management/multilingual/#changes-in-hugo-01120 |
a3419a2
to
dd73164
Compare
With hugo v0.73.0 https://github.com/gohugoio/hugo/releases/tag/v0.73.0, the following values were replaced: taxonomy -> term & taxonomyTerm -> taxonomy With hugo v0.112.0 custom parameters are to be defined within languages.xx.params https://gohugo.io/content-management/multilingual/#changes-in-hugo-01120
dd73164
to
06477a9
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: SaschaSchwarze0 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Changes
Removes deprecated variables from config.toml
Submitter Checklist
Release Notes