Re: [DISCUSS] Flagon CI

[Joshua Poore]

Yep!

I updated ours to be consistent with our testing/support strategy (they were 
quite dated): 

  "engines": {
"node": "^16.x || ^18.x",
"npm": "^8.x || ^9.x”

Yarn and other bundlers should throw a warning if the Node/Npm versions don’t 
match. Node won’t do anything, unless the —engine-strict flag is on in calls to 
nom. That should answer the mail on what we’re testing against and plan to 
support, but won’t explicitly prevent people using older versions from using 
flagon. Added some simple text in the Readme on this.

Other things:

- Node 19.x will only have security support for 4 more months (not actively 
support). It’s throwing some issues with JSDOM. Not presently adding to CI 
strategy, as a result. It may work though when I bump JSDOM.

-  Another thing to remember in all of this is that flagon-useralejs doesn’t 
actually have any true dependencies. We specify “dev dependencies” only—you 
only need those dependencies when using our build pipleine (the script itself 
is pre-built and bundled). If I recall, that factors into how module bundlers 
handle collisions between packages and engines.

Dependency tree is clean now. Maybe time to spin a patch release… 

> On Feb 3, 2023, at 10:05 PM, jason_y54  
> wrote:
> 
> Looking at the npm docs, we can specify versions of npm we support in 
> package.json without requiring them.
> 
> For example:
> { "engines" : { "npm" : "~1.0.20" } }
> 
> Read more here:
> 
> https://docs.npmjs.com/cli/v6/configuring-npm/package-json 
> 
> 
> On Fri, Feb 3, 2023 at 6:23 PM, Joshua Poore  > wrote:
> 
>> Complete agreement with that!
>> 
>> With nothing else heard this week, I’ll bump our CI versions.
>> 
>> I think maybe we can put together (or find) a badge we can put on GitHub 
>> Readme to indicate “supported versions.
>> 
>> Now, supported versions are different than compatible versions… while I 
>> think we should only “support” certain versions of NODE, I don’t think I’m 
>> for forcing that, i.e., enforcing supported version through node engine 
>> params in package.json. I think if users want to use old versions of node, 
>> they can, but at their own risk with no expectation (from us) of support.
>> 
>> Thoughts there?
>> 
>> Josh
>> 
>>> On Jan 30, 2023, at 11:56 PM, Austin Bennett  wrote:
>>> 
>>> Supportive of that.
>>> 
>>> Would encourage us to also communicate more general guidance on what the 
>>> community intends to support [ or can expect ]. An example --> "We support 
>>> 3 versions of Node, at least 2 of which are LTS". Or something similar. 
>>> Good for website, README, etc...
>>> 
>>> Also, very strongly suggest that we consider stopping support of versions 
>>> once versions are EOL, given potential related security concerns. 
>>> Concretely thinking ahead, node16 is EOL 11 Nov 2023 [ 1 ]. After that 
>>> point ( once EOL ) software is increasingly dangerous to continue to use, 
>>> not to mention harder to support.
>>> 
>>> 
>>> [1] https://nodejs.org/en/blog/announcements/nodejs16-eol/ 
>>>  
>>> >> >
>>> On Mon, Jan 30, 2023 at 8:42 PM Joshua Poore >>  >> >> wrote:
>>> Silly me—I forgot to couch this in the context of UserALE.js! For the 
>>> avoidance of doubt...
>>> 
 On Jan 30, 2023, at 11:37 PM, Joshua Poore >>>  >> wrote:
 
 All,
 
 I’ve been doing some simple dependency management—mostly for security, and 
 to stay on top of modernization.
 
 We’re about at that time when some of the versions of Node.js that we test 
 against are nearing (or past) the end of life [1].
 
 Consistent with [1], I think we should be testing and supporting Node vs. 
 16.x, 18.x, 19.x. Currently we are (CI) testing against 12.x, 14.x, 16.x.
 
 Before, we commit to any specific versions—I just wanted to pulse the 
 community to see if anyone strongly opposes the proposal above, given the 
 Node versions they are using.
 
 Let’s discuss for 72 hours. I’ll continue maintenance in the interim.
 
 Josh
 
 [1] https://endoflife.date/nodejs  
 >

Re: [DISCUSS] Flagon CI

[jason_y54]

Looking at the npm docs, we can specify versions of npm we support in 
package.json without requiring them.

For example:
{ "engines" : { "npm" : "~1.0.20" } }

Read more here:

https://docs.npmjs.com/cli/v6/configuring-npm/package-json

On Fri, Feb 3, 2023 at 6:23 PM, Joshua Poore  wrote:

> Complete agreement with that!
>
> With nothing else heard this week, I’ll bump our CI versions.
>
> I think maybe we can put together (or find) a badge we can put on GitHub 
> Readme to indicate “supported versions.
>
> Now, supported versions are different than compatible versions… while I think 
> we should only “support” certain versions of NODE, I don’t think I’m for 
> forcing that, i.e., enforcing supported version through node engine params in 
> package.json. I think if users want to use old versions of node, they can, 
> but at their own risk with no expectation (from us) of support.
>
> Thoughts there?
>
> Josh
>
>> On Jan 30, 2023, at 11:56 PM, Austin Bennett  wrote:
>>
>> Supportive of that.
>>
>> Would encourage us to also communicate more general guidance on what the 
>> community intends to support [ or can expect ]. An example --> "We support 3 
>> versions of Node, at least 2 of which are LTS". Or something similar. Good 
>> for website, README, etc...
>>
>> Also, very strongly suggest that we consider stopping support of versions 
>> once versions are EOL, given potential related security concerns. Concretely 
>> thinking ahead, node16 is EOL 11 Nov 2023 [ 1 ]. After that point ( once EOL 
>> ) software is increasingly dangerous to continue to use, not to mention 
>> harder to support.
>>
>>
>> [1] https://nodejs.org/en/blog/announcements/nodejs16-eol/ 
>> 
>> On Mon, Jan 30, 2023 at 8:42 PM Joshua Poore > > wrote:
>> Silly me—I forgot to couch this in the context of UserALE.js! For the 
>> avoidance of doubt...
>>
>> > On Jan 30, 2023, at 11:37 PM, Joshua Poore > > > wrote:
>> >
>> > All,
>> >
>> > I’ve been doing some simple dependency management—mostly for security, and 
>> > to stay on top of modernization.
>> >
>> > We’re about at that time when some of the versions of Node.js that we test 
>> > against are nearing (or past) the end of life [1].
>> >
>> > Consistent with [1], I think we should be testing and supporting Node vs. 
>> > 16.x, 18.x, 19.x. Currently we are (CI) testing against 12.x, 14.x, 16.x.
>> >
>> > Before, we commit to any specific versions—I just wanted to pulse the 
>> > community to see if anyone strongly opposes the proposal above, given the 
>> > Node versions they are using.
>> >
>> > Let’s discuss for 72 hours. I’ll continue maintenance in the interim.
>> >
>> > Josh
>> >
>> > [1] https://endoflife.date/nodejs 
>>

Re: [DISCUSS] Flagon CI

[Joshua Poore]

added a quick badge to Readme to indicate Node.js support—up on test. Comments?

https://github.com/apache/incubator-flagon-useralejs/tree/test

> On Feb 3, 2023, at 9:23 PM, Joshua Poore  wrote:
> 
> Complete agreement with that!
> 
> With nothing else heard this week, I’ll bump our CI versions.
> 
> I think maybe we can put together (or find) a badge we can put on GitHub 
> Readme to indicate “supported versions.
> 
> Now, supported versions are different than compatible versions… while I think 
> we should only “support” certain versions of NODE, I don’t think I’m for 
> forcing that, i.e., enforcing supported version through node engine params in 
> package.json. I think if users want to use old versions of node, they can, 
> but at their own risk with no expectation (from us) of support.
> 
> Thoughts there?
> 
> Josh
> 
>> On Jan 30, 2023, at 11:56 PM, Austin Bennett > > wrote:
>> 
>> Supportive of that.  
>> 
>> Would encourage us to also communicate more general guidance on what the 
>> community intends to support [ or can expect ].  An example --> "We support 
>> 3 versions of Node, at least 2 of which are LTS".  Or something similar.  
>> Good for website, README, etc...
>> 
>> Also, very strongly suggest that we consider stopping support of versions 
>> once versions are EOL, given potential related security concerns.  
>> Concretely thinking ahead, node16 is EOL 11 Nov 2023 [ 1 ].  After that 
>> point ( once EOL ) software is increasingly dangerous to continue to use, 
>> not to mention harder to support.  
>> 
>> 
>> [1] https://nodejs.org/en/blog/announcements/nodejs16-eol/ 
>> >  >
>> On Mon, Jan 30, 2023 at 8:42 PM Joshua Poore >  > >> wrote:
>> Silly me—I forgot to couch this in the context of UserALE.js! For the 
>> avoidance of doubt...
>> 
>>> On Jan 30, 2023, at 11:37 PM, Joshua Poore >>  >> >> wrote:
>>> 
>>> All,
>>> 
>>> I’ve been doing some simple dependency management—mostly for security, and 
>>> to stay on top of modernization.
>>> 
>>> We’re about at that time when some of the versions of Node.js that we test 
>>> against are nearing (or past) the end of life [1].
>>> 
>>> Consistent with [1], I think we should be testing and supporting Node vs. 
>>> 16.x, 18.x, 19.x. Currently we are (CI) testing against 12.x, 14.x, 16.x.
>>> 
>>> Before, we commit to any specific versions—I just wanted to pulse the 
>>> community to see if anyone strongly opposes the proposal above, given the 
>>> Node versions they are using. 
>>> 
>>> Let’s discuss for 72 hours. I’ll continue maintenance in the interim.
>>> 
>>> Josh
>>> 
>>> [1] https://endoflife.date/nodejs 
>>> >> >

Re: [DISCUSS] Flagon CI

[Joshua Poore]

Complete agreement with that!

With nothing else heard this week, I’ll bump our CI versions.

I think maybe we can put together (or find) a badge we can put on GitHub Readme 
to indicate “supported versions.

Now, supported versions are different than compatible versions… while I think 
we should only “support” certain versions of NODE, I don’t think I’m for 
forcing that, i.e., enforcing supported version through node engine params in 
package.json. I think if users want to use old versions of node, they can, but 
at their own risk with no expectation (from us) of support.

Thoughts there?

Josh

> On Jan 30, 2023, at 11:56 PM, Austin Bennett  wrote:
> 
> Supportive of that.  
> 
> Would encourage us to also communicate more general guidance on what the 
> community intends to support [ or can expect ].  An example --> "We support 3 
> versions of Node, at least 2 of which are LTS".  Or something similar.  Good 
> for website, README, etc...
> 
> Also, very strongly suggest that we consider stopping support of versions 
> once versions are EOL, given potential related security concerns.  Concretely 
> thinking ahead, node16 is EOL 11 Nov 2023 [ 1 ].  After that point ( once EOL 
> ) software is increasingly dangerous to continue to use, not to mention 
> harder to support.  
> 
> 
> [1] https://nodejs.org/en/blog/announcements/nodejs16-eol/ 
> 
> On Mon, Jan 30, 2023 at 8:42 PM Joshua Poore  > wrote:
> Silly me—I forgot to couch this in the context of UserALE.js! For the 
> avoidance of doubt...
> 
> > On Jan 30, 2023, at 11:37 PM, Joshua Poore  > > wrote:
> > 
> > All,
> > 
> > I’ve been doing some simple dependency management—mostly for security, and 
> > to stay on top of modernization.
> > 
> > We’re about at that time when some of the versions of Node.js that we test 
> > against are nearing (or past) the end of life [1].
> > 
> > Consistent with [1], I think we should be testing and supporting Node vs. 
> > 16.x, 18.x, 19.x. Currently we are (CI) testing against 12.x, 14.x, 16.x.
> > 
> > Before, we commit to any specific versions—I just wanted to pulse the 
> > community to see if anyone strongly opposes the proposal above, given the 
> > Node versions they are using. 
> > 
> > Let’s discuss for 72 hours. I’ll continue maintenance in the interim.
> > 
> > Josh
> > 
> > [1] https://endoflife.date/nodejs 
> 

Re: [DISCUSS] Flagon CI

[Austin Bennett]

Supportive of that.

Would encourage us to also communicate more general guidance on what the
community intends to support [ or can expect ].  An example --> "We support
3 versions of Node, at least 2 of which are LTS".  Or something similar.
Good for website, README, etc...

Also, very strongly suggest that we consider stopping support of versions
once versions are EOL, given potential related security concerns.
Concretely thinking ahead, node16 is EOL 11 Nov 2023 [ 1 ].  After that
point ( once EOL ) software is increasingly dangerous to continue to use,
not to mention harder to support.


[1] https://nodejs.org/en/blog/announcements/nodejs16-eol/

On Mon, Jan 30, 2023 at 8:42 PM Joshua Poore  wrote:

> Silly me—I forgot to couch this in the context of UserALE.js! For the
> avoidance of doubt...
>
> > On Jan 30, 2023, at 11:37 PM, Joshua Poore  wrote:
> >
> > All,
> >
> > I’ve been doing some simple dependency management—mostly for security,
> and to stay on top of modernization.
> >
> > We’re about at that time when some of the versions of Node.js that we
> test against are nearing (or past) the end of life [1].
> >
> > Consistent with [1], I think we should be testing and supporting Node
> vs. 16.x, 18.x, 19.x. Currently we are (CI) testing against 12.x, 14.x,
> 16.x.
> >
> > Before, we commit to any specific versions—I just wanted to pulse the
> community to see if anyone strongly opposes the proposal above, given the
> Node versions they are using.
> >
> > Let’s discuss for 72 hours. I’ll continue maintenance in the interim.
> >
> > Josh
> >
> > [1] https://endoflife.date/nodejs
>
>

Re: [DISCUSS] Flagon CI

[Joshua Poore]

Silly me—I forgot to couch this in the context of UserALE.js! For the avoidance 
of doubt...

> On Jan 30, 2023, at 11:37 PM, Joshua Poore  wrote:
> 
> All,
> 
> I’ve been doing some simple dependency management—mostly for security, and to 
> stay on top of modernization.
> 
> We’re about at that time when some of the versions of Node.js that we test 
> against are nearing (or past) the end of life [1].
> 
> Consistent with [1], I think we should be testing and supporting Node vs. 
> 16.x, 18.x, 19.x. Currently we are (CI) testing against 12.x, 14.x, 16.x.
> 
> Before, we commit to any specific versions—I just wanted to pulse the 
> community to see if anyone strongly opposes the proposal above, given the 
> Node versions they are using. 
> 
> Let’s discuss for 72 hours. I’ll continue maintenance in the interim.
> 
> Josh
> 
> [1] https://endoflife.date/nodejs

[DISCUSS] Flagon CI

[Joshua Poore]

All,

I’ve been doing some simple dependency management—mostly for security, and to 
stay on top of modernization.

We’re about at that time when some of the versions of Node.js that we test 
against are nearing (or past) the end of life [1].

Consistent with [1], I think we should be testing and supporting Node vs. 16.x, 
18.x, 19.x. Currently we are (CI) testing against 12.x, 14.x, 16.x.

Before, we commit to any specific versions—I just wanted to pulse the community 
to see if anyone strongly opposes the proposal above, given the Node versions 
they are using. 

Let’s discuss for 72 hours. I’ll continue maintenance in the interim.

Josh

[1] https://endoflife.date/nodejs