Update changelog.mdx

[zisom-hc]

Why

Fix a typo with the release date of 1.4.0

What

Before: 05/10/2022 After: 10/05/2022

---

Merge Checklist

If items do not apply to your changes, add (N/A) and mark them as complete.

Pull Request

• [ ] One or more labels describe the type of change (e.g. clarification) and associated product (e.g. tfc).
• [ ] Description links to related pull requests or issues, if any.

Content

• [ ] Redirects have been added for moved, renamed, or deleted pages. This requires a separate PR in the terraform-website repository redirects.next.js file.
• [ ] API documentation and the API Changelog have been updated.
• [ ] Links to related content where appropriate (e.g., API endpoints, permissions, etc.).
• [ ] Pages with related content are updated and link to this content when appropriate.
• [ ] Sidebar navigation files have been updated for added, deleted, reordered, or renamed pages.
• [ ] New pages have metadata (page name and description) at the top.
• [ ] New images are 2048 px wide. They have HashiCorp standard annotation color (#F92672) and format (rectangle with rounded corners), blurred sensitive details (e.g. credentials, usernames, user icons), and descriptive alt text in the markdown for accessibility.
• [ ] New code blocks have the correct syntax and line breaks to eliminate horizontal scroll bars.
• [ ] UI elements (button names, page names, etc.) are bolded.
• [ ] The Vercel website preview successfully deployed.

Reviews

• [ ] I or someone else reviewed the content for technical accuracy.
• [ ] I or someone else reviewed the content for typos, punctuation, spelling, and grammar.

[vercel[bot]]

@zisom-hc is attempting to deploy a commit to the HashiCorp Team on Vercel.

A member of the Team first needs to authorize it.

[ryanuber]

Woops! That definitely looks wrong. FYI this is generated by the tfc-agent repo's CHANGELOG, so if we only fix it here it will get overwritten on the next release. I'd recommend updating it there first, then we can merge this.

[ryanuber]

Also in case you are curious: you can see the usual flow of how this is updated in the RELEASING.md guide:

Generate a pull request to update the agent's changelog on the public website. You can do this by running the make changelog_website command from the root of this repository. You will see the updates get pushed to a new branch. Make sure you open the PR - this final step is not automatic.

[zisom-hc]

Good to know how this works; thanks for the insight. Turns out i don't have permissions to edit, create a branch, or fork the repo within the tfc-agent repo :sadpanda:. Would you be able to grant permissions, or make the change on my behalf?

[ryanuber]

I just opened up the permissions such that you should have write access, which should allow you to make branches and push code to them. In theory that should allow the UI-based editing to work. Can you give that a rip?

[zisom-hc]

Thanks for opening up the permissions for me. I see that Natalie already took care of the typo within the changelog for the sake of the 1.6.0 release, so i'll go ahead and close this out, but will create a proper PR within the tfc-agent repo in the future