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

Update mongodb/laravel-mongodb dependency to version 5.1 #156

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

alfinauzikri
Copy link

Description

Updated the mongodb/laravel-mongodb dependency to version 5.1 to ensure compatibility with the latest features and security updates.

Motivation and context

This change is required to keep the project dependencies up-to-date and to leverage the improvements and bug fixes in the new version of mongodb/laravel-mongodb.

How has this been tested?

The changes have been tested by running the existing test suite to ensure that all functionalities work as expected with the updated dependency. Additionally, manual testing was performed in the development environment to verify the integration.

Screenshots (if appropriate)

image

Types of changes

What types of changes does your code introduce? Put an x in all the boxes that apply:

  • 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 change)

Checklist:

Go over all the following points, and put an x in all the boxes that apply.

Please, please, please, don't send your pull request until all of the boxes are ticked. Once your pull request is created, it will trigger a build on our continuous integration server to make sure your tests and code style pass.

  • I have read the CONTRIBUTING document.
  • My pull request addresses exactly one patch/feature.
  • I have created a branch for this patch/feature.
  • Each individual commit in the pull request is meaningful.
  • I have added tests to cover my changes.
  • If my change requires a change to the documentation, I have updated it accordingly.

@jimmyazji
Copy link

I had to change use Jenssegers\Mongodb\Schema\Blueprint; to use MongoDB\Laravel\Schema\Blueprint; after publishing the migration, Other than that I think it works perfectly out of the box.

Tyvm!

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