Skip to content
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.

Sign up for GitHub

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

Jump to bottom

fix: bump axios and contentful management [NONE] #1260

Merged
merged 3 commits into from
Oct 23, 2023
Merged

fix: bump axios and contentful management [NONE] #1260

merged 3 commits into from
Oct 23, 2023

Conversation

Vinz93
Copy link
Contributor

@Vinz93 Vinz93 commented Oct 23, 2023 •
edited
Loading

Chore 🧹

  • bump Typescript version to 4.9.4
  • bump contentful-management to 11.2.0
  • bump Axios 1.5.1
  • bump @types/node 20.8.7

@Vinz93 Vinz93 marked this pull request as ready for review October 23, 2023 12:23
@Vinz93 Vinz93 requested a review from a team as a code owner October 23, 2023 12:23
marcolink
marcolink approved these changes Oct 23, 2023
View reviewed changes
Copy link
Member

@marcolink marcolink left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's make it a fix version to enforce a new release maybe?

@Vinz93 Vinz93 changed the title chore: bump axios and contentful management [NONE] fix: bump axios and contentful management [NONE] Oct 23, 2023
@Vinz93 Vinz93 merged commit 9e1bfbb into master Oct 23, 2023
2 checks passed
@Vinz93 Vinz93 deleted the chore/bump-axios-and-contentful-management branch October 23, 2023 13:59
@contentful-automation
Copy link

🎉 This PR is included in version 4.17.2 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@marcolink marcolink marcolink approved these changes

Assignees
No one assigned
Labels
released
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
2 participants
@Vinz93 @marcolink