`Provided ruleset is not an object` error after upgrading from 1.37.12 to 1.37.13
@diatrcz y travaille déjà.
Depuis le 13/7/2026.
Évaluation
Cette issue n'a pas encore été évaluée.
Description
We're seeing this error when trying to upgrade to the latest package:
iqp-service:openapi:validation: [ERROR] There was a problem with spectral.
iqp-service:openapi:validation: [ERROR] Provided ruleset is not an object
iqp-service:openapi:validation: [ERROR] Additional error details:
iqp-service:openapi:validation: [ERROR] RulesetValidationError: Provided ruleset is not an object
iqp-service:openapi:validation: at assertValidRuleset (/workspace/app/device-management/node_modules/ibm-openapi-validator/node_modules/@stoplight/spectral-core/dist/ruleset/validation/assertions.js:12:15)
iqp-service:openapi:validation: at new Ruleset (/workspace/app/device-management/node_modules/ibm-openapi-validator/node_modules/@stoplight/spectral-core/dist/ruleset/ruleset.js:35:44)
iqp-service:openapi:validation: at Spectral.setRuleset (/workspace/app/device-management/node_modules/ibm-openapi-validator/node_modules/@stoplight/spectral-core/dist/spectral.js:66:73)
iqp-service:openapi:validation: at setup (/workspace/app/device-management/node_modules/ibm-openapi-validator/src/spectral/index.js:160:12)
iqp-service:openapi:validation: at async runSpectral (/workspace/app/device-management/node_modules/ibm-openapi-validator/src/spectral/index.js:34:20)
iqp-service:openapi:validation: at async runValidator (/workspace/app/device-management/node_modules/ibm-openapi-validator/src/cli-validator/run-validator.js:234:17) {
iqp-service:openapi:validation: code: 'invalid-ruleset-definition',
iqp-service:openapi:validation: path: []
iqp-service:openapi:validation: }
device-service:openapi:validation: [ERROR] There was a problem with spectral.
device-service:openapi:validation: [ERROR] Provided ruleset is not an object
device-service:openapi:validation: [ERROR] Additional error details:
device-service:openapi:validation: [ERROR] RulesetValidationError: Provided ruleset is not an object
device-service:openapi:validation: at assertValidRuleset (/workspace/app/device-management/node_modules/ibm-openapi-validator/node_modules/@stoplight/spectral-core/dist/ruleset/validation/assertions.js:12:15)
device-service:openapi:validation: at new Ruleset (/workspace/app/device-management/node_modules/ibm-openapi-validator/node_modules/@stoplight/spectral-core/dist/ruleset/ruleset.js:35:44)
device-service:openapi:validation: at Spectral.setRuleset (/workspace/app/device-management/node_modules/ibm-openapi-validator/node_modules/@stoplight/spectral-core/dist/spectral.js:66:73)
device-service:openapi:validation: at setup (/workspace/app/device-management/node_modules/ibm-openapi-validator/src/spectral/index.js:160:12)
device-service:openapi:validation: at async runSpectral (/workspace/app/device-management/node_modules/ibm-openapi-validator/src/spectral/index.js:34:20)
device-service:openapi:validation: at async runValidator (/workspace/app/device-management/node_modules/ibm-openapi-validator/src/cli-validator/run-validator.js:234:17) {
device-service:openapi:validation: code: 'invalid-ruleset-definition',
device-service:openapi:validation: path: []
device-service:openapi:validation: }
We run the tool like this:
lint-openapi -s --impact-score -r .spectral.yml -w 370 src/modules/openapi/openapi-spec.json
Here is the .spectral.yml in this case:
extends: '@ibm-cloud/openapi-ruleset'
rules:
ibm-enum-casing-convention: warn
ibm-required-array-properties-in-response: warn
# GET /workloads returns a usage status, this is not returned for sessions or legacy jobs (old pricing model)
# added as a warning to unblock us for now but we should try to resolve this
ibm-required-enum-properties-in-response: warn
- Langage dominant
- JavaScript
- Étoiles
- 635
- Forks
- 98
- Merge moyen
- 1 j 5 h
- PR mergées (30 j)
- 8
Préparer son environnement
- Fournit un Dockerfile ou un fichier Docker Compose
- Propose un modèle de pull request
- Lire le guide de contribution
Par où commencer
- Lisez l'issue en entier, puis le guide de contribution du projet.
- Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
- Forkez le dépôt et travaillez sur une branche.
- Ouvrez une pull request qui référence le numéro de l'issue.
Autres issues de IBM/openapi-validator
-
security
Difficulté 2/5 1-3 heures Accessibilité débutants 52/100
IBM/openapi-validator#875 · 1 commentaire ·
-
Difficulté 3/5 1-2 jours Accessibilité débutants 45/100
IBM/openapi-validator#748 · 4 commentaires ·
-
Difficulté 3/5 1-2 jours Accessibilité débutants 42/100
IBM/openapi-validator#747 · 2 commentaires · 1 réaction ·
-
Difficulté 4/5 3-5 jours Accessibilité débutants 32/100
IBM/openapi-validator#643 · 3 commentaires ·
-
Difficulté 5/5 Plus d'une semaine Accessibilité débutants 25/100
IBM/openapi-validator#545 · 1 commentaire ·
Toutes les issues de IBM/openapi-validator
Issues similaires
-
Difficulté 2/5 1-3 heures Accessibilité débutants 68/100
Les mainteneurs répondent en général sous 1 jour
-
Difficulté 2/5 1-3 heures Accessibilité débutants 82/100
jonathanong/no-mistakes#3332 ·
Les mainteneurs répondent en général sous 1 jour
-
documentation
Difficulté 2/5 1-3 heures Accessibilité débutants 72/100
githubnext/gh-aw-workshop#5674 ·
Les mainteneurs répondent en général sous 1 jour
-
更新已收录主题套装为三主题及管理器兼容说明Ouverte
Difficulté 1/5 Moins d'une heure Accessibilité débutants 62/100
awesome-dsh-plugin/awesome-dsh-plugin#14970 ·
Les mainteneurs répondent en général sous 1 jour
-
bug
Difficulté 2/5 1-3 heures Accessibilité débutants 72/100
swc-project/swc-ai-issues#653 ·