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

Release 1.0 #208

Merged
merged 30 commits into from
Jul 26, 2024
Merged

Release 1.0 #208

merged 30 commits into from
Jul 26, 2024

Conversation

dougwilson
Copy link
Contributor

@dougwilson dougwilson commented Feb 3, 2022

This is a tracking issue for release 1.0.

I am trying to give better visibility for upcoming changes and so am trying out making a PR for a release here, pulling from the official next release branch into master. This allows for the current pending changes to be easily visible.

Please keep feature requests in their own issues

I'm also leaving this PR unlocked so people can make comments/etc. and we'll see how it goes :) If you want to make a comment on a particular change, please make the comment in the "Files changed" tab so comments are not lost during a rebase.

List of changes for release:

List of deprecated things removed:

  • send.etag()
  • send.hidden() and hidden option
  • send.index()
  • send.maxage()
  • send.root()

Testing this release

If you want to try out this release, you can install it with the following command:

$ npm install pillarjs/send#1.0

Owners/collaborators: please do not merge this PR :)

@hello-smile6

This comment was marked as resolved.

@dougwilson

This comment was marked as resolved.

@hello-smile6

This comment was marked as resolved.

@dougwilson

This comment was marked as resolved.

@hello-smile6

This comment was marked as resolved.

@pillarjs pillarjs deleted a comment from SukkaW Aug 21, 2022
@wesleytodd
Copy link
Member

@pillarjs/express-tc could I get a few eyes on this? I bumped a bunch of deps to latest, changed over to ^ ranges so we dont have as much work to do on this in the future, but otherwise this is older changes. If I can get an approval just double checking this I will publish the 1.0 and then update express@5 to use it and mark it off on expressjs/discussions#233

@wesleytodd wesleytodd merged commit 56b1817 into master Jul 26, 2024
4 checks passed
@wesleytodd
Copy link
Member

I published 1.0.0 on the next dist tag, we can bump that to latest when we are ready to handle any support issues for that. Since I was unable to get more validation on this than just bumping it in express I went with that here expressjs/express#5786.

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.

4 participants