ref: simplify docker build workflow

[jordanrfrazier]

Docker Build: https://github.com/langflow-ai/langflow/actions/runs/11700357489/job/32584217961

This pull request includes significant updates to the Docker build and push workflows, primarily focusing on enhancing the flexibility and clarity of version and release type handling. The most important changes include renaming and adding new input parameters, updating job steps to accommodate these changes, and refining the tagging and versioning logic.

Enhancements to Input Parameters:

• Renamed version to main_version and added base_version with detailed descriptions for better clarity. (.github/workflows/docker-build.yml, .github/workflows/docker-build.ymlL5-R48)
• Updated the release_type parameter to include more detailed descriptions and added a ref parameter to specify the reference to check out. (.github/workflows/docker-build.yml, .github/workflows/docker-build.ymlL5-R48)

Updates to Job Steps:

• Removed the Resolve nightly tag step and replaced it with a verification step to ensure a main version exists. (.github/workflows/docker-build.yml, .github/workflows/docker-build.ymlL63-R126)
• Adjusted the Get Version to Tag step to handle both main_version and base_version appropriately based on the release type. (.github/workflows/docker-build.yml, .github/workflows/docker-build.ymlL63-R126)
• Streamlined the logic for checking out code and setting up the environment based on the new input parameters. (.github/workflows/docker-build.yml, .github/workflows/docker-build.ymlL211-R187)

Refinements to Tagging and Versioning Logic:

• Updated the tagging logic to include both specific version tags and the latest tag for pre-releases. (.github/workflows/docker-build.yml, .github/workflows/docker-build.ymlL186-R157)
• Simplified the conditions for nightly builds and removed redundant steps related to nightly tags. (.github/workflows/docker-build.yml, .github/workflows/docker-build.ymlL174-R144)

Changes to Release Workflow:

• Modified the release workflow to use the new main_version and base_version parameters, ensuring that both base and main versions are passed correctly. (.github/workflows/release.yml, .github/workflows/release.ymlL192-R218)

[ogabrielluiz]

LGTM

btw, we can add an entrypoint to the default image if you like

[jordanrfrazier]

LGTM

btw, we can add an entrypoint to the default image if you like

@zzzming Any reason you think we'd want to keep the images separate in the future?

[phact]

LGTM
btw, we can add an entrypoint to the default image if you like

@zzzming Any reason you think we'd want to keep the images separate in the future?

Looks like langflow-frontend and langflow-backend have usage, 5k and 6k pulls respectively. Do we want to delete them?

[phact]

LGTM
btw, we can add an entrypoint to the default image if you like

@zzzming Any reason you think we'd want to keep the images separate in the future?

Looks like langflow-frontend and langflow-backend have usage, 5k and 6k pulls respectively. Do we want to delete them?

This is addressed in the latest code.

changes LGTM, nightly action passes https://github.com/langflow-ai/langflow/actions/runs/11710303423 +1