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

Fix Gemfile.lock mismatch with Gemfile #479

Merged
merged 1 commit into from
Oct 1, 2024

Conversation

jayjay-w
Copy link
Contributor

@jayjay-w jayjay-w commented Oct 1, 2024

Fix Gemfile.lock mismatch with Gemfile.

Description

This mismatch was introduced in #477 where we updated the pg gem version in Gemfile and did not update the same in Gemfile.lock

References: CV2-4958

Checklist

  • I have performed a self-review of my own code
  • I have added unit and feature tests, if the PR implements a new feature or otherwise would benefit from additional testing
  • I have added regression tests, if the PR fixes a bug
  • I have added logging, exception reporting, and custom tracing with any additional information required for debugging
  • I considered secure coding practices when writing this code. Any security concerns are noted above.
  • I have commented my code in hard-to-understand areas, if any
  • I have made needed changes to the README
  • My changes generate no new warnings
  • If I added a third party module, I included a rationale for doing so and followed our current guidelines

Fix Gemfile.lock mismatch with Gemfile. This mismatch was introduced in #477
@jayjay-w jayjay-w merged commit d37f85b into develop Oct 1, 2024
3 of 4 checks passed
@jayjay-w jayjay-w deleted the CV2-4958-fix-gemfile-mismatch branch October 1, 2024 18:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants