Skip to content

Merge v1.17 into v1.18 #1339

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

Merged
merged 2 commits into from
Jun 6, 2024
Merged

Merge v1.17 into v1.18 #1339

merged 2 commits into from
Jun 6, 2024

Conversation

mongodb-php-bot
Copy link
Collaborator

Merge new changes from v1.17 into v1.18.

Commits

Resolving conflicts

To resolve any conflicts, check out the temporary branch and run the following command:
git merge v1.18

Ignoring changes

To ignore from the remote branch, first reset the temporary branch to v1.18 and manually merge using the `ours` merge strategy:
git reset --hard v1.18
git merge --strategy=ours v1.17

Then, push the temporary branch to upate the pull request.

jmikola added 2 commits May 23, 2024 13:10
Prefer "extension" over "driver" when referring to ext-mongodb specifically.

Also removes mention of Int64 having a private constructor.

* PHPLIB-1466: Remove obsolete "Type Map Limitations"
@mongodb-php-bot mongodb-php-bot requested a review from a team as a code owner June 6, 2024 17:22
@mongodb-php-bot mongodb-php-bot requested a review from alcaeus June 6, 2024 17:22
@jmikola jmikola removed the request for review from alcaeus June 6, 2024 17:24
@jmikola jmikola merged commit 464ca05 into v1.18 Jun 6, 2024
7 of 9 checks passed
@jmikola jmikola deleted the merge-v1.17-into-v1.18-1717694575528 branch June 6, 2024 17:27
This was referenced Jun 6, 2024
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