v0.6.2

What's Changed

• hotfix: error raised for short series by @MMenchero in #31
• feat: add Azure endpoints by @MMenchero in #35
• feat: infer business-day frequency by @MMenchero in #36
• fix: issue with Date objects by @MMenchero in #37
• docs: add azure vignette by @MMenchero in #39

Full Changelog: v0.6.1...v0.6.2

v0.6.1

What's Changed

• Update NEWS.md by @tracykteal in #28
• fix: release v0.6.0 issues by @MMenchero in #27
• feat: vectorized date generation by @MMenchero in #29

Full Changelog: v0.6.0...v0.6.1

v0.6.0

v0.6.0

Breaking changes

• The time_col parameter now only accepts values in the formats YYYY-MM-DD and YYYY-MM-DD hh:mm:ss, either as character strings or date objects (Date class or POSIXct class).
• The id_col parameter now defaults to unique_id for all core functions.
• Minimum data requirements have been implemented, following the new TimeGPT API-v2 specifications.
• Changes to the allowed frequency aliases have been made. For more details, see the "Special Topics" vignette.

Features

• Extended support to tibbles for input data.
• Exogenous variables no longer require future values. Users can now provide only the historical values of exogenous variables.

Bug fixes

• Fixed an issue where timestamps such as "2024-01-01 00:00:00" were sometimes converted to "2024-01-01".

Documentation

• Vignettes have been updated to reflect the new features and changes.

Full Changelog: v0.5.4...v0.6.0

v0.5.4

What's Changed

Version 0.5.4 of nixtlar is now available. This development release introduces parallel processing, which are not yet available on CRAN and can be used to handle large datasets. To use this feature, configure the num_partitions parameter in any of the nixtlar methods as follows:

• num_partitions=NULL: This is the default setting, operating in sequential mode, equivalent to num_partitions=1.
• num_partitions="auto": Automatically uses all available resources as determined by future::availableCores().
• num_partitions can be set to any positive integer. If it exceeds the number of available resources determined by future::availableCores(), it will default to the maximum available cores.

Full Changelog: v0.5.3...v0.5.4

v0.5.3

Release v0.5.3 - Development Version

Welcome to version 0.5.3 of the nixtlar package. This development release introduces several features that are not yet available on CRAN. Here’s what’s new:

• Quantile Forecasts: This update includes the ability to perform quantile forecasts. To learn how to use this new feature, check out our Quantile Forecasts Vignette.

• Comprehensive Documentation: We've expanded our documentation to make it easier for you to use nixtlar effectively. Explore the new and updated vignettes here.

• Improved API Stability: nixtlar now includes automatic retries for requests that fail due to intermittent API errors.

• Updated API URLs: This version uses the new URLs for the TimeGPT API. Please note that while the URLs in the CRAN version are still operational, they will be deprecated in the future. We will make an announcement before this change takes place.

New Contributors

• @tracykteal made their first contribution in #2