change org for dbt_versent_dimensional_automate package

[merisaindajang-versent]

Description

This package provides dbt macros to automate building Type 1 & Type 2 dimensions and fact tables, removing the need for manual SCD logic. It ensures data integrity, historical tracking, and consistency across models while scaling efficiently on large datasets. Example templates are included to help you get started quickly.

I have added this package in another PR before, but since the organisation name is wrong, it seems that it does not appear in the dbt hub package at all. here is the linked PR #378

Link to your package's repository:
https://github.com/Versent/dbt_versent_dimensional_automate.git

Checklist

This checklist is a cut down version of the best practices that we have identified as the package hub has grown. Although meeting these checklist items is not a prerequisite to being added to the Hub, we have found that packages which don't conform provide a worse user experience.

First run experience

• (Required): The package includes a licence file detectable by GitHub, such as the Apache 2.0 or MIT licence.
• The package includes a README which explains how to get started with the package and customise its behaviour
• The README indicates which data warehouses/platforms are expected to work with this package

Customisability

• The package uses ref or source, instead of hard-coding table references.

Dependencies

Dependencies on dbt Core

• The package has set a supported require-dbt-version range in dbt_project.yml. Example: A package which depends on functionality added in dbt Core 1.2 should set its require-dbt-version property to [">=1.2.0", "<2.0.0"].

Dependencies on other packages defined in packages.yml:

• Dependencies are imported from the dbt Package Hub when available, as opposed to a git installation.
• Dependencies contain the widest possible range of supported versions, to minimise issues in dependency resolution.
• In particular, dependencies are not pinned to a patch version unless there is a known incompatibility.

Interoperability

• The package does not override dbt Core behaviour in such a way as to impact other dbt resources (models, tests, etc) not provided by the package.
• The package uses the cross-database macros built into dbt Core where available, such as {{ dbt.except() }} and {{ dbt.type_string() }}.
• The package disambiguates its resource names to avoid clashes with nodes that are likely to already exist in a project. For example, packages should not provide a model simply called users.

Versioning

• (Required): The package's git tags validates against the regex defined in hubcap/version.py (examples).
• The package's version follows the guidance of Semantic Versioning 2.0.0. (Note in particular the recommendation for production-ready packages to be version 1.0.0 or above)

[joellabes]

@merisaindajang-versent this is now picking up your repo, but not matching any tags. I think it's because your V is uppercase, so this checkbox is inaccurate:

(Required): The package's git tags validates against the regex defined in hubcap/version.py (examples).

[merisaindajang-versent]

Hi @joellabes , thank you for your review! I have updated the tags, so do you reckon it should be picking up the package now and showing in the https://hub.getdbt.com/ ?

[joellabes]

Looks like it! https://hub.getdbt.com/versent/dbt_versent_dimensional_automate/latest/