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

Backport CI changes to 5.x.x branch #672

Closed
wants to merge 2 commits into from

Conversation

Seldaek
Copy link
Contributor

@Seldaek Seldaek commented Jul 28, 2021

Seldaek and others added 2 commits July 28, 2021 13:32
… right class (JsonSchema\Constraints\Constraint instead of JsonSchema\Constraints\BaseConstraint). Closes jsonrainbow#654 (jsonrainbow#655)

Co-authored-by: Emmanuel GUITON <egn@intrinsec.com>
Co-authored-by: Jordi Boggiano <j.boggiano@seld.be>
Copy link
Collaborator

@DannyvdSluijs DannyvdSluijs left a comment

Choose a reason for hiding this comment

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

@Seldaek I've done a review and I only think that due to time some other ports (see below) are needed as well. Just let me know what you think, I can help out with those ports as well.

Oher backports to consider for this PR:


steps:
- name: "Checkout"
uses: "actions/checkout@v2"
Copy link
Collaborator

Choose a reason for hiding this comment

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

Due to time passing this should now be v4

Suggested change
uses: "actions/checkout@v2"
uses: "actions/checkout@v4"


steps:
- name: "Checkout"
uses: "actions/checkout@v2"
Copy link
Collaborator

Choose a reason for hiding this comment

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

Suggested change
uses: "actions/checkout@v2"
uses: "actions/checkout@v4"


steps:
- name: "Checkout"
uses: "actions/checkout@v2"
Copy link
Collaborator

Choose a reason for hiding this comment

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

Suggested change
uses: "actions/checkout@v2"
uses: "actions/checkout@v4"


- name: Run PHPStan
run: |
composer require --dev phpstan/phpstan:^0.12.93 marc-mabe/php-enum-phpstan ${{ env.COMPOSER_FLAGS }}
Copy link
Collaborator

Choose a reason for hiding this comment

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

Suggested change
composer require --dev phpstan/phpstan:^0.12.93 marc-mabe/php-enum-phpstan ${{ env.COMPOSER_FLAGS }}
composer require --dev phpstan/phpstan:^1.5 marc-mabe/php-enum-phpstan ${{ env.COMPOSER_FLAGS }}

In cd8ec4f you've updated to version 1.5 of PHPStan


steps:
- name: "Checkout"
uses: "actions/checkout@v2"
Copy link
Collaborator

Choose a reason for hiding this comment

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

Suggested change
uses: "actions/checkout@v2"
uses: "actions/checkout@v4"

@@ -1,6 +1,6 @@
# JSON Schema for PHP

[![Build Status](https://travis-ci.org/justinrainbow/json-schema.svg?branch=master)](https://travis-ci.org/justinrainbow/json-schema)
[![Build Status](https://github.com/justinrainbow/json-schema/actions/workflows/continuous-integration.yml/badge.svg)](https://github.com/justinrainbow/json-schema/actions)
Copy link
Collaborator

Choose a reason for hiding this comment

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

Suggested change
[![Build Status](https://github.com/justinrainbow/json-schema/actions/workflows/continuous-integration.yml/badge.svg)](https://github.com/justinrainbow/json-schema/actions)
[![Build Status](https://github.com/jsonrainbow/json-schema/actions/workflows/continuous-integration.yml/badge.svg)](https://github.com/jsonrainbow/json-schema/actions)

@@ -20,10 +20,10 @@
'phpdoc_no_package' => false,
Copy link
Collaborator

Choose a reason for hiding this comment

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

If we want to make this update date from the current master should we also port 19ed8ac in?

@Seldaek
Copy link
Contributor Author

Seldaek commented May 27, 2024

Hey tbh i think I'd bury this PR as well as v5.. Focus on moving forward. Once v6 is out there's no reason to keep using v5 imo

@DannyvdSluijs
Copy link
Collaborator

Closing as per author indication which I helps with the focus for v6.0.0

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.

3 participants