Skip to content

Issue to trigger new releases #39

Closed

Description

@ablaom
No description provided.

Activity

  1. pinned this issue on Mar 4, 2024
  2. pebeto commented on Mar 5, 2024

    @pebeto
    Member

    @JuliaRegistrator register branch=main

    Release notes:

    (fix)

    • Solving Documenter pipeline failing on building
    • Increasing project maintainability
    • Increasing code test coverage
  3. JuliaRegistrator commented on Mar 5, 2024

    @JuliaRegistrator

    Registration pull request created: JuliaRegistries/General/102333

    Tagging

    After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

    This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

    git tag -a v0.4.6 -m "<description of version>" a31b41a91dc32107fa7dcd6ad5a581c116a4ff9c
    git push origin v0.4.6
    
  4. pebeto commented on Apr 15, 2024

    @pebeto
    Member

    @JuliaRegistrator register branch=main

    Release notes:

    Addings

    • URI default to ENV["MLFLOW_TRACKING_URI"] if exists, just as mlflow documentation mentions.
  5. JuliaRegistrator commented on Apr 15, 2024

    @JuliaRegistrator

    Registration pull request created: JuliaRegistries/General/104952

    Tagging

    After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

    This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

    git tag -a v0.4.7 -m "<description of version>" c843be3df3488376f41038e3c499c8a07f946639
    git push origin v0.4.7
    
  6. pebeto commented on May 17, 2024

    @pebeto
    Member

    @JuliaRegistrator register branch=main

    Release notes:

    • Moved baseuri to apiroot, allowing users to specify its own API route (improving compatibility with platforms)
    • Removed healthcheck function due to lack of support. It is not working on every platform providing a mlflow instance
    • Added a MLFLOW_TRACKING_URI check when running tests
  7. JuliaRegistrator commented on May 17, 2024

    @JuliaRegistrator

    Registration pull request created: JuliaRegistries/General/107077

    Tagging

    After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

    This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

    git tag -a v0.5.1 -m "<description of version>" 050fa81a1319201fa91e1d17070eed5baa9fca50
    git push origin v0.5.1
    

    Also, note the warning: Version 0.5.1 skips over 0.5.0
    This can be safely ignored. However, if you want to fix this you can do so. Call register() again after making the fix. This will update the Pull request.

  8. pebeto commented on Feb 10, 2025

    @pebeto
    Member

    @JuliaRegistrator register branch=main

    Release notes:

    • New project structure to ensure better maintainability.
    • Adopting Blue Style to improve readability.
    • Pair with all the types from MLflow REST API.
    • Implement all the endpoints from MLflow latest release.
    • Improved documentation with multiple dispatch definitions.
    • Simplify function definitions.
    • Simplify test definitions.

    Important

    This update comes with some breaking changes. Projects like MLJFlow.jl will need to update carefully. It will be the same with personal projects.

  9. JuliaRegistrator commented on Feb 10, 2025

    @JuliaRegistrator

    Registration pull request created: JuliaRegistries/General/124745

    Tagging

    After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

    This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

    git tag -a v0.6.0 -m "<description of version>" d0dee22e741ed4b3da0cd18878446befe9fee36f
    git push origin v0.6.0
    
  10. pebeto commented on Feb 12, 2025

    @pebeto
    Member

    @JuliaRegistrator register branch=main

    Release notes:

    • Two new parameters in MLFlow instance constructor: username and password.
      • These will be injected to the Authorization header for each call to the server.
      • In the case username, password, and the Authorization header are provided, the instantiation will throw an error indicating that you can't do that.
    • Allowing MLFLOW_TRACKING_USERNAME and MLFLOW_TRACKING_PASSWORD environment variables to set the username and password respectively.
  11. JuliaRegistrator commented on Feb 12, 2025

    @JuliaRegistrator

    Registration pull request created: JuliaRegistries/General/124884

    Tagging

    After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

    This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

    git tag -a v0.6.1 -m "<description of version>" c03c83b6dfab27e06257f55d2ad1ea89f50967eb
    git push origin v0.6.1
    
  12. pebeto commented on Aug 18, 2025

    @pebeto
    Member

    @JuliaRegistrator register branch=main

    Release notes:

    • Allowing compatibility with mlflow v3.x.x
      • Upgraded types with last changes in the API specification
      • Implemented logmodel function
  13. JuliaRegistrator commented on Aug 18, 2025

    @JuliaRegistrator

    Registration pull request created: JuliaRegistries/General/136921

    Tagging

    After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

    This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

    git tag -a v0.7.0 -m "<description of version>" b5bad100618832f15d7b9e8f40e1e2e17b281554
    git push origin v0.7.0
    
  14. pebeto commented on Aug 18, 2025

    @pebeto
    Member

    @JuliaRegistrator register branch=main

    Release notes:

    Breaking changes

    • Allowing compatibility with mlflow v3.x.x
      • Upgraded types with last changes in the API specification
      • Implemented logmodel function
  15. JuliaRegistrator commented on Aug 18, 2025

    @JuliaRegistrator

    Registration pull request updated: JuliaRegistries/General/136921

    Tagging

    After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

    This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

    git tag -a v0.7.0 -m "<description of version>" b5bad100618832f15d7b9e8f40e1e2e17b281554
    git push origin v0.7.0
    
  16. ablaom commented on Feb 5, 2026

    @ablaom
    MemberAuthor

    @JuliaRegistrator register branch=main

  17. JuliaRegistrator commented on Feb 5, 2026

    @JuliaRegistrator

    Registration pull request created: JuliaRegistries/General/147706

    Recommendation: add release notes

    Release notes help your users know what has changed in the new version. For breaking releases in particular, it's recommended to document what breaking changes were made (or point to where changes can be found, such as a changelog).

    To add release notes, just add markdown formatted text underneath the comment after the text "Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the release that TagBot creates. i.e.

    @JuliaRegistrator register
    
    Release notes:
    
    ## Breaking changes
    
    - blah
    

    To add release notes to this registration, just re-invoke JuliaRegistrator and the PR will be updated.

    Tagging

    After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

    This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

    git tag -a v0.7.1 -m "<description of version>" bc0e99a3b59fc89e1756c965eb20fdbe0acdfcbb
    git push origin v0.7.1
    
  18. pebeto commented on Apr 13, 2026

    @pebeto
    Member

    @JuliaRegistrator register branch=main

    Release notes:

    New features

    • MLFlow 3.0 API Endpoints
      • Scorers API
      • Gateway API (Databricks-specific)
        • Secrets management
        • Model definitions
        • Endpoints
        • Endpoint bindings
        • Budgets
      • Prompt optimization API
      • MLFlow Artifacts API

    Modifications (breaking changes)

    • logmetric
      • Added parameters: model_id, dataset_name, dataset_digest`

    Notes

    • Gateway API
      • Gateway endpoints are Databricks-specific features
      • Tests will automatically skip if not using a Databricks tracking URI
      • Warning message displayed when attempting to run gateway tests on non-Databricks servers
    • Prompt optimization API
      • Requires evaluation datasets to be present on the server
      • Tests gracefully skip with warnings if required resources are not available
    • MLFlow Artifacts API
      • Uses mlflow-artifacts prefix (separate from main MLFlow API)
      • Multipart upload support for large files
  19. JuliaRegistrator commented on Apr 13, 2026

    @JuliaRegistrator

    Registration pull request created: JuliaRegistries/General/152827

    Tagging

    After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

    This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

    git tag -a v0.8.0 -m "<description of version>" 1bd31f531f34f9caef55d145e1750439548e2661
    git push origin v0.8.0
    
  20. pebeto commented on Apr 17, 2026

    @pebeto
    Member

    @JuliaRegistrator register branch=main

    Release notes:

    New features

    • Gateway services now work on any MLflow 3.x server (removed Databricks-only restriction)
    • updategatewaymodeldefinition and updategatewayendpoint now expose all REST API parameters
    • WebhookEntity.BUDGET_POLICY enum value added
    • Dict constructors for FileInfo and MultipartUploadCredential
    • Webhook docs page added; missing entries added to existing doc pages

    Bug fixes

    • updaterun: run_name now defaults to missing; fixed Integer(missing) crash when status omitted
    • detachmodelfromgatewayendpoint: changed from DELETE to POST
    • testwebhook: fixed response key ("result" not "test_result")
    • listwebhooks: empty page_token no longer sent (caused server INTERNAL_ERROR)
    • searchexperiments, searchruns, searchregisteredmodels, searchmodelversions: same empty-string fix
    • createexperiment: workaround for MLflow 3.x basic-auth permission race condition
    • GatewayEndpoint: Added experiment_id and usage_tracking fields
    • Removed dead mlfpatch_v3 function

    Breaking changes

    • WebhookStatus.INACTIVE renamed to DISABLED
    • WebhookEntity.PROMPT_VERSION_ALIAS renamed to PROMPT_ALIAS
    • attachmodeltogatewayendpoint returns GatewayEndpointModelMapping instead of GatewayEndpoint
    • Gateway type fields renamed (creation_timestamp to created_at, and update_timestamp to last_updated_at)
    • GatewayEndpoint.model_configs renamed to model_mappings
    • Search functions: filter/page_token type changed from String to Union{String,Missing}
    • updategatewayendpoint: config param replaced with explicit API fields

    Note

    Previous version (v0.8.0) was tested against a mlflow==3.10 installation. An error occurred while updating, so apologies for the inconvenience.

  21. JuliaRegistrator commented on Apr 17, 2026

    @JuliaRegistrator

    Registration pull request created: JuliaRegistries/General/153183

    Tagging

    After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

    This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

    git tag -a v0.9.0 -m "<description of version>" 516dc7760c13da07057fdd8c57cf81219cf1d7bf
    git push origin v0.9.0
    
  22. pebeto commented on Jul 13, 2026

    @pebeto
    Member

    @JuliaRegistrator register branch=main

    Release notes:

    New features

    • Full MLflow 3.14 REST API coverage
      • Workspaces
      • RBAC: roles and per-user permissions
      • Label schemas
    • Managed MLflow test server via CondaPkg (tests no longer require an external server), with parallel CI across Julia versions

    Bug fixes

    • HTTP.jl 2.x: send Connection: close to avoid unexpected EOF while reading HTTP/1 data from stale keep-alive connections against MLflow's server
    • Error handling now rethrows connection/parse errors (e.g. HTTP.ParseError) instead of masking them with a FieldError on e.response
    • Replaced deprecated readtimeout with read_idle_timeout in the test-server health check
    • Webhook tests: pin MLFLOW_WEBHOOK_SECRET_ENCRYPTION_KEY so multi-worker MLflow 3.14 servers can decrypt webhook secrets (fixes an intermittent 500 on webhook delete)

    Breaking changes

    • Requires HTTP.jl 2
    • Per-resource permission API removed in favor of RBAC: the ExperimentPermission/RegisteredModelPermission types and the create/get/update/deleteexperimentpermission and create/get/update/deleteregisteredmodelpermission functions are gone
    • Experiment gained a workspace field, so its positional constructor now takes 9 arguments
  23. JuliaRegistrator commented on Jul 13, 2026

    @JuliaRegistrator

    Registration pull request created: JuliaRegistries/General/161239

    Tagging

    After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

    This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

    git tag -a v0.10.0 -m "<description of version>" 4ec92e7a01025889f15e58db0abeafe555606b16
    git push origin v0.10.0
    
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions