Upstream tracker

[pi0]

Tracking upstream changes in jshttp/cookie to be backported.

History: https://github.com/jshttp/cookie/blob/master/HISTORY.md

Types upstream: https://github.com/DefinitelyTyped/DefinitelyTyped/blob/master/types/cookie/index.d.ts

Last check: v0.6.0 (on 29 march 2024)

0.6.0

• jshttp/cookie@84a1567

0.5.0:

• jshttp/cookie@624b4e2
• jshttp/cookie@7c65abe
• jshttp/cookie@042073f
• jshttp/cookie@16ded68

0.4.2:

• jshttp/cookie@009b3cb
• jshttp/cookie@aa1a335

[NozomuIkuta]

How about setting up a workflow that periodically checks the upstream repository and create an issue (or a comment) if it has made changes and/or release since the last execution?

Unfortunately, as far as I researched, there is no way a repository "subscribes" (push) to other repositories' changes.
So we have to set up a workflow that "checks" (pull) the changes by itself.

If you like it, I could work on it.

Refs:

• https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#schedule

[pi0]

That would be a nice idea using (weekly maybe?) schedules. We can keep a file like .upstream with last commit hash in upstream rebased and action to update/create issue if a new one available? (either way feel free to work on it would be cool project!)

[NozomuIkuta]

📝 There is an issue about ESM support in upstream
jshttp/cookie#152

[pi0]

@NozomuIkuta do you still want to work on automation? based the fact the uptes on upstream are not so often, it probably is not that critical for this repo but a generic "fork tracker" applet might be nice idea. It could be a github app for example.