Skip to content

1.20.7 - #767

Merged
UlisesGascon merged 1 commit into
1.xfrom
release/1.20.7
Sep 8, 2026
Merged

1.20.7#767
UlisesGascon merged 1 commit into
1.xfrom
release/1.20.7

Conversation

@UlisesGascon

@UlisesGascon UlisesGascon commented Sep 7, 2026

Copy link
Copy Markdown
Member

Blockers

We need/want to land (waiting for reviews):

What's included in the HISTORY.md

1.20.7
===================

* deps: qs@~6.16.0

What's Changed

Full Changelog: 1.20.6...1.x

@UlisesGascon UlisesGascon self-assigned this Sep 7, 2026
@Phillip9587

Copy link
Copy Markdown
Member

Why are the release dates removed?

@Phillip9587 Phillip9587 left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

LGTM

@UlisesGascon

Copy link
Copy Markdown
Member Author

Why are the release dates removed?

I started to do that in all the packages, the problems with the dates hardcoded is that we need to push changes if we decide to delay or anticipate and that can impact on the approvals on the PRs. So this is more flexible from the releaser perspective. In other packages we are removing the file (HISTORY.md or CHANGELOG.md) as we use already tags and releases on GitHub (but we might lost historical context as some releases were made before gitHub had the release feature included in the platform

@UlisesGascon UlisesGascon changed the title Release: 1.20.7 1.20.7 Sep 8, 2026
@UlisesGascon
UlisesGascon merged commit 0f0f0d7 into 1.x Sep 8, 2026
35 checks passed
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.

body-parser@1.x pins qs to "~6.15.1", blocking security patch releases like 6.16.0

2 participants