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.

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

chore(updatedependencies): update various dependencies #58

Merged
merged 9 commits into from
Jan 13, 2023

Conversation

dogpatch626
Copy link
Contributor

@dogpatch626 dogpatch626 commented Dec 13, 2022

updated various dependencies.

Description

    "@commitlint/cli": "^9.1.2",
    "@commitlint/config-conventional": "^17.3.0",
    "@semantic-release/changelog": "^6.0.0",
    "@semantic-release/commit-analyzer": "^9.0.0",
    "@semantic-release/git": "^10.0.0",
    "@semantic-release/github": "^8.0.0",
    "@semantic-release/npm": "^9.0.0",
    "@semantic-release/release-notes-generator": "^10.0.0",
    "eslint-config-amex": "^15.3.1",
    "jest": "^29.0.0",
    "semantic-release": "^19.0.0"
after updating these packages running npm audit showed 0 vulnerabilities. 

Motivation and Context

How Has This Been Tested?

ran unit tests, they pass needed to update snapshots they're appropriate just a change in back slashes present.
also installed into one app and ran unit tests

Types of Changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation (adding or updating documentation)
  • Dependency update

Checklist:

  • My change requires a change to the documentation and I have updated the documentation accordingly.
  • My changes are in sync with the code style of this project.
  • There aren't any other open Pull Requests for the same issue/update.
  • These changes should be applied to a maintenance branch.
  • I have added the Apache 2.0 license header to any new files created.

What is the Impact to Developers Using amex-jest-preset?

@Matthew-Mallimo
Copy link
Member

Looks like there are conflicts in the package-lock

Copy link
Member

@Matthew-Mallimo Matthew-Mallimo left a comment

Choose a reason for hiding this comment

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

Fix package-lock issues

@Matthew-Mallimo Matthew-Mallimo requested a review from a team December 13, 2022 18:19
@Matthew-Mallimo Matthew-Mallimo requested a review from a team January 3, 2023 14:29
@10xLaCroixDrinker 10xLaCroixDrinker merged commit 757cd68 into main Jan 13, 2023
@10xLaCroixDrinker 10xLaCroixDrinker deleted the chore/update-dependencies branch January 13, 2023 04:53
oneamexbot added a commit that referenced this pull request Jan 13, 2023
# [7.0.0](v6.1.2...v7.0.0) (2023-01-13)

### chore

* **updatedependencies:** update various dependencies ([#58](#58)) ([757cd68](757cd68))

### BREAKING CHANGES

* **updatedependencies:** drop the support of node 10 12 and 14
oneamexbot added a commit that referenced this pull request Jan 18, 2023
# [7.0.0](v6.1.2...v7.0.0) (2023-01-18)

### Bug Fixes

* **commitlint:** extend footer length ([#60](#60)) ([6da5f71](6da5f71))

### chore

* **updatedependencies:** update various dependencies ([#58](#58)) ([757cd68](757cd68))

### BREAKING CHANGES

* **updatedependencies:** drop the support of node 10 12 and 14
oneamexbot added a commit that referenced this pull request Jan 18, 2023
# [7.0.0](v6.1.2...v7.0.0) (2023-01-18)

### Bug Fixes

* **commitlint:** extend footer length ([#60](#60)) ([6da5f71](6da5f71))

### chore

* **updatedependencies:** update various dependencies ([#58](#58)) ([757cd68](757cd68))

### BREAKING CHANGES

* **updatedependencies:** drop the support of node 10 12 and 14
@oneamexbot
Copy link
Contributor

🎉 This PR is included in version 7.0.0 🎉

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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants