When updating an R package version, should you update the licence year too?

When you first make the R package, you tend to make the licence with that initial year of the first version.

I was wondering if you should update the year in the licence when you release an update after that? Or what is best practice here?

E.g. my licence in my R package is 2022 when I first created it. Now I am about to release a major new version. Should I update it 2024?

Yes, update it to 2022--2024.

1 Like

Cool, thanks @Gabor Tidyverse packages often seem to have a single year though, rather than a range?

I recently tried to find an authoritative source on whether to use the current date or a range when asserting copyright (I also mentioned this in the related thread Package's annual maintenance - #2 by jdblischak). I found lots of conflicting advice online. I've always used date ranges, but more and more I see only the current date. As a concrete example, the footer on the GitHub website only states "2024"


1 Like

Yeah, we should do a better job with this.

1 Like

I did some more searching. From what I can tell, including the original date is important because it helps determine when the copyright will expire.


1 Like

Thanks @jdblischak and @Gabor

Seems like all approaches are valid. Therefore, I lean towards just leaving it as original_year to avoid the hassle/complexity of continually updating it

1 Like

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.

If you have a query related to it or one of the replies, start a new topic and refer back with a link.