Skip to content

Release candidate - #39

Merged
jwrosewell merged 15 commits into
mainfrom
rc
Nov 4, 2026
Merged

jwrosewell merged 15 commits into
mainfrom
rc

Conversation

@jwrosewell

Copy link
Copy Markdown
Contributor

Releases what has collected on rc since #37:

  • #38 Look for the resource keys link the cloud engine now gives in the cloud tests

The publish of #37 (run 41918913736) failed in every Test job on the two cloud tests #38 fixes, so it pushed nothing to PyPI and made no tags. This release changes only those tests, and its publish builds and releases the packages #37 changed, at the versions #37 would have given them.

No commit asks for a major or minor version change, so the publish moves only patch numbers.

The last release into main was #37, merged at 21:40 UTC on 4 November 2026.

jwrosewell and others added 15 commits November 3, 2026 21:02
* Point the documentation build at the example folders and package

List the cloud request engine examples and the device detection examples
source folder in EXAMPLE_PATH, so Doxygen finds the files the examples
name. Include each client hints example's template from its own folder,
and read the location package from src/fiftyone_location.

* Keep the cloud web example doc comment unbroken and name its view by folder

* Keep the onpremise web example doc comment unbroken and name its view by folder
…25)

* Point links to the archived repositories at where the code now lives

The examples, readmes and example web pages linked to the archived
Python repositories, and the IP Intelligence readmes linked to the
archived IP Intelligence C repository. Each link now points at the same
file or folder in 51degrees-python, or at the IP Intelligence readme in
51degrees-cxx, so readers land on code that is still maintained.

Links to a file follow the file to its folder in this repository, for
example the Device Detection examples now sit under
device-detection/fiftyone_devicedetection_examples/src. Links that used
the old version/4.5 branch now use main.

The match metrics example closed its Markdown link with a square bracket
instead of a parenthesis. The link now closes with a parenthesis. The
cloud examples readme changes into the cloned folder after cloning, so
its cd line now follows the new clone address.

The history table in the root README still names the earlier
repositories, because their tags and releases stay there. The links to
the data repositories are unchanged, because those repositories are
still current.

* Describe the IP Intelligence performance test gap without old repository names
* Add a temporary workflow that generates the SWIG wrappers for 51degrees-cxx 4.5.102

* Name the SWIG modules in the temporary workflow instead of reading them

* Generate both SWIG wrappers again for 51degrees-cxx 4.5.102

Between 4.5.100 and 4.5.102, 51degrees-cxx removed the two
EngineHash process overloads and the three EngineIpi process
overloads that take required property indexes. The committed
wrappers still called them, so neither on-premise package compiled
against 4.5.102, which the nightly submodule update brings in #26.

This moves the cxx submodule from 4110d681, the 4.5.100 release, to
1bec7b57, the 4.5.102 release, and generates hash_python_wrap.cxx,
DeviceDetectionHashEngineModule.py, ipi_python_wrap.cxx and
IpIntelligenceEngineModule.py again with SWIG 4.4.1 built from its
v4.4.1 tag. Run against 4110d681, the same command gives files byte
for byte the same as the ones committed before, so every difference
here comes from cxx. Both engines call only process(evidence), which
cxx keeps.

* Remove the temporary SWIG wrapper workflow
Co-authored-by: Automation51D <51DCI@51Degrees.com>
@jwrosewell
jwrosewell marked this pull request as ready for review November 4, 2026 23:05
@jwrosewell
jwrosewell merged commit 0b4081a into main Nov 4, 2026
2 checks passed
jwrosewell added a commit that referenced this pull request Nov 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants