Skip to content

Release v6.2.0: Security updates and dependency upgrades#438

Open
daniloab wants to merge 3 commits intomasterfrom
release/prepare-v6.2.0
Open

Release v6.2.0: Security updates and dependency upgrades#438
daniloab wants to merge 3 commits intomasterfrom
release/prepare-v6.2.0

Conversation

@daniloab
Copy link
Copy Markdown
Collaborator

Summary

This PR consolidates fixes from multiple open PRs into a single release that addresses critical security vulnerabilities and updates dependencies.

Security Fixes

  • ✅ Migrate from swagger-parser to @apidevtools/swagger-parser (v12.1.0)
    • Fixes multiple security vulnerabilities in json-schema-ref-parser
    • Updates to latest OpenAPI validation schemas
  • ✅ Update body-parser to 1.20.4+ (fixes qs DoS vulnerability CVE-2025)
  • ✅ Update express to 4.22.1+ (fixes qs vulnerability)
  • ✅ Update yaml from 2.0.0-1 to 2.8.1 (latest stable with security patches)
  • ✅ Update npm-run-all to npm-run-all2 (6.2.6) - actively maintained fork
  • ✅ Update supertest to 7.1.4 (latest)

npm audit Results

  • Production dependencies: 0 vulnerabilities ✅
  • DevDependencies: 5 moderate (eslint-related dev tools only, no runtime impact)

Test Results

  • ✅ 48/50 tests passing (96% success rate)
  • ✅ All core functionality working
  • ✅ All integration tests passing
  • ⚠️ 2 tests failing: cross-document YAML anchor/alias feature (edge case)

Breaking Changes

YAML Library Upgrade (1.x → 2.x)

  • parseDocument options now passed as parameter instead of global config
  • Error message formats changed (YAMLParseError vs YAMLSyntaxError/YAMLSemanticError)
  • Stricter validation of YAML structures

Known Limitations

Cross-document YAML anchor/alias references have changed behavior due to YAML 2.x stricter validation. The feature mostly works, but complex cross-file anchor scenarios may require adjustment. This affects AWS API Gateway integration templates that use external anchor references.

Related PRs Consolidated

Test Plan

  • Run full test suite
  • Run npm audit
  • Verify core functionality with examples
  • Check backward compatibility

🤖 Generated with Claude Code

daniloab and others added 3 commits January 30, 2026 15:01
## Security Fixes
- Migrate from swagger-parser to @apidevtools/swagger-parser (v12.1.0)
  - Fixes multiple security vulnerabilities in json-schema-ref-parser
  - Updates to latest OpenAPI validation schemas
- Update body-parser to 1.20.4+ (fixes qs DoS vulnerability)
- Update express to 4.22.1+ (fixes qs vulnerability)
- Update yaml from 2.0.0-1 to 2.8.1 (latest stable)
  - Includes security patches and API improvements
- Update npm-run-all to npm-run-all2 (6.2.6) - maintained fork
- Update supertest to 7.1.4 (latest)

## Breaking Changes
- YAML library upgraded to 2.x with API changes
  - parseDocument options now passed as parameter
  - Anchor/alias handling updated for YAML 2.x stricter validation
  - Error messages format changed (YAMLParseError vs YAMLSyntaxError)

## Test Updates
- Updated test snapshots for new YAML error message formats
- Updated error message assertions to match YAML 2.x output
- 48/50 tests passing (96% success rate)

## Known Limitations
- Cross-document YAML anchor/alias references have changed behavior
  due to YAML 2.x stricter validation. Most use cases work, but
  complex cross-file anchor scenarios may need adjustment.

## Dependencies Audit
- Production dependencies: 0 vulnerabilities
- DevDependencies: 5 moderate (eslint-related, dev-only tools)

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
- 48/50 tests passing (96%)
- 0 production vulnerabilities
- Cross-document YAML anchors/aliases known limitation
- All core functionality working
@a-kriya
Copy link
Copy Markdown

a-kriya commented Feb 17, 2026

Why is this titled 6.2.0? That version has already been out for a few years? Did you mean 6.3.0?

@buti1021
Copy link
Copy Markdown

Hey @daniloab anything we can do to support get this out? As @a-kriya mentioned, 6.2.1 has been the last release. Thanks for keeping this alive and all the best! :)

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.

3 participants