Release 2.16

[nachocodoner]

meteor update --release 2.16
# or 
meteor create appname --release  2.16

We'll make sure Meteor 3.x isn't affected by new additions in this release. Tracking progress on PR #13098.

Best Candidates

These are the top PR candidates for the next release, focusing on Meteor 3.x migration. Original authors will address any necessary checks, with the core team reviewing for compatibility with both 2.x and future 3.x versions.

• 339 Support observeChangesAsync and observeAsync [Meteor 2.x]

• New mongo package options to optimize Oplog tailing performance to include/exclude certain collections
  New mongo package options to optimize Oplog tailing performance to include/exclude certain collections #13009

Quick Gains

These PRs are straightforward and expected to integrate smoothly into Meteor 3.x, offering immediate benefits. We will double check them on a release-3.0 based-branch.

• chore: remove repetitive words
  chore: remove repetitive words #13093

• Get default options from meteor settings
  Get default options from meteor settings #13005

• Session storage option for accounts
  Session storage option for accounts #13046

• check - throw all errors
  feat: check - throw all errors #12970

• Add nodemailer-openpgp
  Add nodemailer-openpgp #12991

Hotfixes

Update terser to v5.31.0
#13120

Discarded

Other PRs are currently excluded from the upcoming release due to the effort needed for verification and potential impact on Meteor 3.x transition, which remains our primary focus.

DDP resumption
#12436

Update Accounts with Async methods
#12647

Remove underscore
#12245
#12261
#12259
#12238
#12267

Asyncify _checkForCaseInsensitiveDuplicates
#13076

---

Any other PR to be considered for including in 2.16 release must point release-2.16 branch, update to latest changes, have green checks on that branch, and ask for a review keeping the PR alive.

[StorytellerCZ]

Got an interesting error when trying to update:

While selecting package versions:
error: No version of logging satisfies all constraints: @1.3.4-beta2160.1, @=1.3.3, @~1.3.4-beta2160.1
Constraints on package "logging":
* [email protected] <- top level
* logging@=1.3.3 <- top level
* logging@~1.3.4-beta2160.1 <- top level
* [email protected] <- webapp 1.13.8 <- accounts-oauth 1.4.4-beta2160.1 <- accounts-facebook 1.3.3
* [email protected] <- webapp 1.13.8 <- communitypackages:fast-render 3.3.1
* [email protected] <- mongo 1.16.10-beta2160.1
* [email protected] <- percolate:migrations 1.0.3
* [email protected] || 1.3.1 || 1.3.3-beta300.6 <- reywood:publish-composite 1.8.8
* [email protected] <- email 2.2.6-beta2160.1
* [email protected] <- oauth 2.2.1 <- accounts-oauth 1.4.4-beta2160.1 <- accounts-facebook 1.3.3
* [email protected] <- oauth 2.2.1 <- bozhao:link-accounts 2.8.0
* [email protected] <- storyteller:fictionaltime 0.4.1

Given that this is a patch update, I wonder if this one is the issue:

[email protected] || 1.3.1 || 1.3.3-beta300.6 <- reywood:publish-composite 1.8.8

This looks like an issue with the 3.0 release having an overlap with an existing package release.

Update: After updating to reywood:publish-composite and storyteller:fictionaltime to have the latest 3.0-rc.0 in their versionsFrom resolution they disappeared from the list, so I think that need to be fixed in other packages if the app wants to update for the beta. I think this won't be a problem after the full release.

Update 2: So in the end it seems to be something at the top level that is forcing the 1.3.3 version of the logging package. Even if I remove the package from my packages list it, this line still remains: * logging@=1.3.3 <- top level

[StorytellerCZ]

I think we can move to RC here.