release v1.1.0

[jameslamb]

Release v1.1.0.

It looks like {futile.logger} ended up putting up a new release that fixes CRAN's checks (https://cran.r-project.org/web/packages/futile.logger/index.html), so no time pressure on this.

But even with #259 a non-issue now, I still think we should do this to reduce the risk of something like it happening again. {futile.logger} wasn't providing that much value here.

Release checklist

Copied from #253

Before merging:

• finish remaining issues/PRs
• see a full CI run pass (and no ERRORs, WARNINGs, or NOTEs from R CMD check) on this branch
• get an approval on this PR from @austin3dickey
• build package tarball from this branch and submit it to CRAN
• update cran-comments.md on this branch once the package is (hopefully) accepted and passing checks
• update conda-forge recipe (https://github.com/conda-forge/r-uptasticsearch-feedstock)
• merge this PR

After merging:

1. tag that commit on main as v1.1.0
2. create a new release at https://github.com/uptake/uptasticsearch/releases
3. put up another PR setting the version to 1.1.0.9999 (update development version to 1.1.0.9999 #263)

Notes for Reviewers

N/A

[austin3dickey]

looks great!

[jameslamb]

Great, thanks! I've submitted v1.1.0 to CRAN, will keep you posted.

[jameslamb]

Still a few platforms that haven't been checked / had binaries built yet.

ref: https://cran.r-project.org/web/checks/check_results_uptasticsearch.html

I'll check back again later this week.

[jameslamb]

CRAN has built binaries for all the platforms it supports and only 2 checks (r-release-windows-x86_64 and r-patched-linux-x86_64) remain.

That's good enough, let's merge this and finish the release. I've updated cran-comments.md.

[jameslamb]

Created the tag + release: https://github.com/uptake/uptasticsearch/releases/tag/v1.1.0

I think we're done here, thanks as always Austin 🤝