npm-check-updates is only updated to the next minor version

MartinX3 · 2022-09-07 22:04:30

I don't know why, but each time the package gets flagged out of date it's only upgraded to the next minor version.
Is there some reason why it isn't just updated to the newest version?
It's useless to use every little outdated version.

https://archlinux.org/packages/communit … k-updates/

loqs · 2022-09-07 23:26:52

~~https://github.com/npm/cli/releases/tag/v8.19.1 tagged as latest which matches the version Arch is packaging. What newer version are you referring to and where can it be obtained?~~
Edit:
Sorry for the noise somehow I pulled the git for npm-cli instead of bpm-check-updates.

Last edited by loqs (2022-09-08 00:06:36)

Loader009 · 2022-09-08 13:06:01

@felixonmars - no comment on this?

Lone_Wolf · 2022-09-09 09:28:19

https://github.com/archlinux/svntogit-c … ates/trunk

Looks like it has been updated, version is now 16.0.1 .

MartinX3 · 2022-09-09 09:41:24

Lone_Wolf wrote:

https://github.com/archlinux/svntogit-c … ates/trunk
Looks like it has been updated, version is now 16.0.1 .

It get's updated each time I flag it as outdated.
Otherwise it wouldn't get any update.

But upstream is now at 16.1.0 and not 16.0.1.

I started flagging it on Aug 7, 2022 where he updated it to 15.0.1 where upstream already was at 16.0.5

Loader009 · 2022-09-09 09:57:24

Lone_Wolf wrote:

https://github.com/archlinux/svntogit-c … ates/trunk
Looks like it has been updated, version is now 16.0.1 .

Look at the upstream tags -> https://github.com/raineorshine/npm-check-updates/tags
Now look at your commit history.

Do you notice something?

edit: feels like felixonmars is a github commit collector - the more commits, the better for him?

Last edited by Loader009 (2022-09-09 09:59:33)

Daerandin · 2022-09-09 11:08:25

I think you are more likely to get a response if you simply email the maintainer and ask why the arch package is not updated to the newest upstream release. There could be many reasons.

I also feel the need to point out the fact that all Arch devs and TU's are volunteers who spend their free time on Arch.

Loader009 wrote:

Lone_Wolf wrote:
https://github.com/archlinux/svntogit-c … ates/trunk
Looks like it has been updated, version is now 16.0.1 .
Look at the upstream tags -> https://github.com/raineorshine/npm-check-updates/tags
Now look at your commit history.
Do you notice something?
edit: feels like felixonmars is a github commit collector - the more commits, the better for him?

Comments like this one does not help in any way. I can only speculate on the intent of this comment, but I want to point out that felixonmars currently have over 3300 packages in the repos. That means there is more than enough work to keep up with, and definitely a lot more useful contributions to Arch than your current attitude.

MartinX3 · 2022-09-09 11:52:34

Daerandin wrote:

I think you are more likely to get a response if you simply email the maintainer and ask why the arch package is not updated to the newest upstream release. There could be many reasons.
I also feel the need to point out the fact that all Arch devs and TU's are volunteers who spend their free time on Arch.

I know and I already tried it last month.
I wrote my message in the "flag text" and added my e-mail.
No response.

Last edited by MartinX3 (2022-09-09 11:52:51)

Loader009 · 2022-09-09 12:05:01

Daerandin wrote:

Comments like this one does not help in any way. I can only speculate on the intent of this comment, but I want to point out that felixonmars currently have over 3300 packages in the repos. That means there is more than enough work to keep up with, and definitely a lot more useful contributions to Arch than your current attitude.

It's not my attitude. If someone is having too much work, then he/she should give the work to someone else. This is just being mindful.
Also - if you want to lower your amount of work, then you would update the package straight to the current version and not just update piece by piece.
You should not try to attack those who criticize, you should try to explain why it's done like this.

I am just pointing out a weird behavior, which I cannot understand at all.

MartinX3 · 2022-09-09 12:07:46

I also don't understand why the work need to be done manually.
I work in the IT sector and the optimal workflow would be

1. CI detects new tag and builds it.
2.1 Build error -> Report to maintainer
2.2 Build succeed -> auto pushing to testing repo
3. after 7 days and no issue reports auto pushing to stable repo
4. repeat step 1 with the newest tag if it differs

Last edited by MartinX3 (2022-09-09 12:08:49)

Arch Linux

#1 2022-09-07 22:04:30

npm-check-updates is only updated to the next minor version

#2 2022-09-07 23:26:52

Re: npm-check-updates is only updated to the next minor version

#3 2022-09-08 13:06:01

Re: npm-check-updates is only updated to the next minor version

#4 2022-09-09 09:28:19

Re: npm-check-updates is only updated to the next minor version

#5 2022-09-09 09:41:24

Re: npm-check-updates is only updated to the next minor version

#6 2022-09-09 09:57:24

Re: npm-check-updates is only updated to the next minor version

#7 2022-09-09 11:08:25

Re: npm-check-updates is only updated to the next minor version

#8 2022-09-09 11:52:34

Re: npm-check-updates is only updated to the next minor version

#9 2022-09-09 12:05:01

Re: npm-check-updates is only updated to the next minor version

#10 2022-09-09 12:07:46

Re: npm-check-updates is only updated to the next minor version

Board footer