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

Tests: don't mark PHP 8.1 & 8.2 tests as experimental #12609

Merged
merged 1 commit into from
Nov 2, 2022
Merged

Conversation

spacedmonkey
Copy link
Contributor

Context

Summary

Relevant Technical Choices

To-do

User-facing changes

Testing Instructions

  • This is a non-user-facing change and requires no QA

This PR can be tested by following these steps:

Reviews

Does this PR have a security-related impact?

Does this PR change what data or activity we track or use?

Does this PR have a legal-related impact?

Checklist

  • This PR addresses an existing issue and I have linked this PR to it in ZenHub
  • I have tested this code to the best of my abilities
  • I have verified accessibility to the best of my abilities (docs)
  • I have verified i18n and l10n (translation, right-to-left layout) to the best of my abilities
  • This code is covered by automated tests (unit, integration, and/or e2e) to verify it works as intended (docs)
  • I have added documentation where necessary
  • I have added a matching Type: XYZ label to the PR

Fixes #

@swissspidy swissspidy changed the title PHP: officially support 8.1 + 8.2 Tests: don't mark PHP 8.1 & 8.2 tests as experimental Nov 2, 2022
@swissspidy swissspidy merged commit 83ebf2b into main Nov 2, 2022
@swissspidy swissspidy deleted the fix/8.0+ branch November 2, 2022 14:53
@swissspidy swissspidy added the Type: Infrastructure Changes impacting testing infrastructure or build tooling label Nov 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Infrastructure Changes impacting testing infrastructure or build tooling
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants