GWeather 3.90.0 (development snapshot) ====================================== Changes since GWeather 40.0 --------------------------- - New major API - Remove uses of deprecated API - Use explicit symbol versioning - Move to gi-docgen for generating the API reference - Remove the widgets, along with the GTK3 dependency - Remove the dependency on gdk-pixbuf - Fix a memory leak in GWeather.Info.get_location_name() [#80] - Use the appropriate Unicode for temperature units [#8] - Support building libgweather with libsoup3 - Translation updates Changes in the locations database --------------------------------- - Add missing Italian capitals of provinces - Add missing Spanish capitals of provinces - Add Petrozavodsk city - Add city Multan, Pakistan and Multan Airport - Add Half Moon Bay for a coastal Bay Area reference - Quetta and Peshawar added (cities in Pakistan) - Added Albany Airport, Western Australia (YABA) - Add Santa Fe city and its airport - Fix Astrakhan' timezone [#83] ================== Version 40.0 ================== - Fix possible uninitialized variable in location entry - Translations updates ================== Version 40.beta ================== - Fix gweather_location_next_child annotations - metno: Use alphabetical 2.0 symbol codes ================== Version 40.alpha.1 ================== This version fixes a few major issues that slipped into the last release: - Fix warnings related to the new application-id and contact-info properties - Fix use-after-free issues when detached locations are used - Fix vala binding issues by removing a left over struct definition ================ Version 40.alpha ================ This version contains a number of API and ABI changes that applications will need to be modified for, including: - An application-id as well as contact information must be provided for every application to use online weather services. For GApplication-based applications, the application ID is prefilled. - All online weather providers are disabled by default, applications should enable those that it has verified it can follow the terms of service for. Note, for example, the requirement to subscribe to the met.no API users mailing-list. - A lot of the getter functions for the location database now return references to objects which the application will need to handle. Applications that use JavaScript or Python bindings should not require special handling for this change. The library was also modified to use a more-efficient Location database format, reducing I/O when instantiated, online weather fetching uses a maximum of 4 decimals in coordinates for queries to enhance caching, and the yr.no backend was renamed to Met.no.