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

github-workflow: improve matrix checks #2

Closed
wants to merge 295 commits into from
Closed

github-workflow: improve matrix checks #2

wants to merge 295 commits into from

Conversation

ssbarnea
Copy link
Owner

garethj2 and others added 30 commits April 19, 2021 07:40
According to https://getcomposer.org/doc/04-schema.md#version it should be:
This must follow the format of X.Y.Z or vX.Y.Z with an optional suffix of -dev, -patch (-p), -alpha (-a), -beta (-b) or -RC. The patch, alpha, beta and RC suffixes can also be followed by a number.

Co-authored-by: Maxim.Kolmakov <maxim.kolmakov@jetbrains.com>
* update ioBroker io-package.json

- introduce common.adminUI and deprecated old materialize flags
- bring back title, because there was a bug in controller/admin still requiring it

* deprecationMessage is only a webstorm supported property so put it in description
- explicitly allow old config via html
- new custom only has json
* Add permissions property in github workflow

* Add additional properties in permissions-event
* Extended elmah.io configuration in appsettings.json

* Unit test of elmah.io configuration in appsettings.json
- Add `hadolint.yml` and `.hadolint.yml` to list of known file names,
  as they are both accepted names since hadolint/hadolint#617

- Remove schema and replace with link to selfhosted schema as discussed
  here: hadolint/hadolint#602 (comment)

- Remove tests for hadolint schema
This regexp allows a number after the suffixes that are supposed to allow them, as stated here https://getcomposer.org/doc/04-schema.md#version

`^v?\d+(((\.\d+)?\.\d+)?\.\d+)?(-dev|((-patch|-p|-alpha|-a|-beta|-b|-RC)(\d+)?))?$`

See https://regexr.com/5rt9b for tests regarding the addition
* also make iobroker json ui working on windows and in other dev dirs

* also add noConfig option to new adminUI attribute for adapters w/o config
…e#1594)

Used VS to format document seemed inconsistent spacing
Also remove the old and unsupported camel-k specific schema
* Add schema for Liquibase

https://docs.liquibase.com/concepts/basic/json-format.html

Created by @sunildabburi
https://github.com/sunildabburi/liquibase-schema

* Latest changes for Liquibase

* Update catalog

* Update catalog.json

* Update liquibase.json
…#1599)

* Remove outdated ui5-manifest schema not owned by SAP UI5

The json.schemastore.org/ui5-manifest.json has not been added by SAP UI5
and is outdated.
Meanwhile we have a SAP Open Source github
https://github.com/sap/ui5-manifest/blob/master/schema.json under
Apache-2.0 License which is referenced with name "UI5 Manifest" here in
JSON Schema Store, see
https://github.com/SchemaStore/schemastore/blob/master/src/api/json/catalog.json#L2281

* remove also test for to be removed outdated schema
Add new values for retry errors
Replace single item enums with consts
Add tests for job retry settings
Missing glob for Avro schema *.avsc files
…e#1602)

* Add linguistic schema version 3.2.0

* Remove UTF-8 BOM
Ice3man543 and others added 28 commits September 22, 2021 08:04
Co-authored-by: joshwoodcock <ltdwoodcock@gmail.com>
* Require version property

* Be more strict with additionalProperties

* Add more documentation links

* Fix settings.spacing.blockGap type

* Fix missing styles.border property in additionalProperties check
…ore#1853)

* Add `forwardingGateway` property for Static Web Apps config

* Fixed lint error
* Add imgbotconfig schema (fixes SchemaStore#1843)

* chore: fix lint
* Update kustomization

- mark bases as deprecated
- add missing schema fields: buildMetadata, helmCharts, helmGlobals,
labels, metadata, openapi, validators

* fix lint checks
…operties (SchemaStore#1847)

* Add plagiarize env merge create option

* Allow additional properties for push instances

Co-authored-by: joshwoodcock <ltdwoodcock@gmail.com>
Signed-off-by: Grant Timmerman <timmerman+devrel@google.com>
Since the configuration file can actually be used across https://webcomponents.dev/, https://components.studio/ and https://backlight.dev/ it makes more sense for its name to be more generic

Thanks 🙇
* Update tsconfig.json schema

* Remove the markdown links

* Updates jsconfig

* Allow markdown in jsconfig
* add configuration for trunk.yaml for schemastore

* Update catalog.json
The contrib doc describes how to add test cases for a schema well and
succinctly. However, as a new contributor, it was not clear that the
`negative_test` exists. This adds a note, keeping it a brief as
possible, to point contributors towards negative tests.
…maStore#1870)

Project templates for TypeScript had been established by some teams to
develop the TypeScript code in the src folder and let the transpiling
happen into the webapp folder. In case of editing the manifest.json in
the TypeScript project we need to enhance the file match.
…e#1867)

* add: GitHub Action workflow trigger workflow_call

* Split GitHub Workflow schema job definitions

There are two flavors of jobs: "normal" jobs, and jobs which call
reusable workflows. Split the two cases using a oneOf schema.

In the previously existing case of a "normal" job, "runs-on" is
required and "uses" is forbidden. In the new case, the inverse is
true: "uses" is required and "runs-on" is forbidden.

The job types are moved into the definitions for the schema, and then
written under the desired `oneOf` block. The "needs" property, shared
between the two, is also moved to a new defintion for reuse.

* Don't require 'description' in workflow_call

For both 'inputs' and 'secrets', the 'description' field is optional,
not required. Correct this error.

* Add test cases for github reusable workflows

* Reusable GitHub Workflows require input 'type'

In reusable GitHub Workflows, which define the `workflow_call`
trigger, the `type` field on inputs is required.

1. Add a negative test case which should fail to validate
2. Mark the field required so that the negative test passes

Co-authored-by: Justin Rittenhouse <jrittenh@nd.edu>
…schema --> OK. (SchemaStore#1872)

* add specif schema v1.1

* Update specif-1.1.json

* Update specif-1.1.json

* Update 03_Requirement-with-Properties.specif.json

* Update 09_Very-Simple-Model-FMC-with-Requirements.specif.json

* Update specif-1.1.json

* Update specif-1.1.json
Adds initial support for checking values used inside matrix:
- recognize os and check its documented values
- support for include/exclude which are arrays of same matrix elements
- recognize experimental flags
- allow extra properties
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment