Skip to content

Releases: babakskr/Conduit-console

Release list

v0.3.7

v0.3.7 Latest
Latest

Choose a tag to compare

View all tags
@babakskr babakskr released this 01 Feb 00:59
v0.3.7
58b6097

🚀 Release v0.3.7

Automated release via git_op.sh

📄 docs/AI_DEV_GUIDELINES.md

  • Type: Description of change...

📄 git_op.sh

     if [[ -n "$notes" ]]; then 
        release_body="${release_body}"$'\n### 📄 '"$file"$'\n'"$notes"$'\n'
     fi
done < <(git grep -l "<component_release_notes>")

git commit -m "release: $target_tag (Docs Updated)"
check_error

echo ">> Pushing to $target_branch..."
git push origin "$target_branch"
check_error

echo ">> Pushing tag..."
git tag -a "$target_tag" -m "Release $target_tag"
git push origin "$target_tag"
check_error

if command -v gh &> /dev/null; then
    gh release create "$target_tag" --title "$target_tag" --notes "$release_body"
    echo -e "${GREEN}✅ Released on GitHub!${NC}"
else
    echo -e "${YELLOW}GitHub CLI missing. Local release only.${NC}"
fi

# If we switched to main, stay there? Or go back? Usually staying on main is safer after release.
# If users want to go back, they can checkout dev again.

}

--- MAIN EXECUTION ---

if [[ $# -eq 0 ]]; then
# No args -> Release on CURRENT branch
command_release "current"
exit 0
fi

if [[ "$1" == "main" ]]; then
# Main arg -> Merge to MAIN and release
command_release "main"
exit 0
fi

while [[ $# -gt 0 ]]; do
case "$1" in
-h|--help) show_help; exit 0 ;;
-ver) show_version; exit 0 ;;
-l|--list) command_list_status; exit 0 ;;
-d)
shift
files_to_delete=()
while [[ $# -gt 0 && ! "$1" =~ ^- ]]; do files_to_delete+=("$1"); shift; done
command_delete_files "${files_to_delete[@]}"
;;
-no)
shift; while [[ $# -gt 0 && ! "$1" =~ ^- ]]; do command_deny_file "$1"; shift; done
;;
-yes)
shift; while [[ $# -gt 0 && ! "$1" =~ ^- ]]; do command_allow_file "$1"; shift; done
;;
*) echo -e "${RED}Unknown option: $1${NC}"; show_help; exit 1 ;;
esac

Assets 2
Loading

v0.3.6

v0.3.6

Choose a tag to compare

View all tags
@babakskr babakskr released this 01 Feb 00:59
v0.3.6
a1cd776

🚀 Release v0.3.6

Automated release via git_op.sh

📄 docs/AI_DEV_GUIDELINES.md

  • Type: Description of change...

📄 git_op.sh

     if [[ -n "$notes" ]]; then 
        release_body="${release_body}"$'\n### 📄 '"$file"$'\n'"$notes"$'\n'
     fi
done < <(git grep -l "<component_release_notes>")

git commit -m "release: $target_tag (Docs Updated)"
check_error

echo ">> Pushing to $target_branch..."
git push origin "$target_branch"
check_error

echo ">> Pushing tag..."
git tag -a "$target_tag" -m "Release $target_tag"
git push origin "$target_tag"
check_error

if command -v gh &> /dev/null; then
    gh release create "$target_tag" --title "$target_tag" --notes "$release_body"
    echo -e "${GREEN}✅ Released on GitHub!${NC}"
else
    echo -e "${YELLOW}GitHub CLI missing. Local release only.${NC}"
fi

# If we switched to main, stay there? Or go back? Usually staying on main is safer after release.
# If users want to go back, they can checkout dev again.

}

--- MAIN EXECUTION ---

if [[ $# -eq 0 ]]; then
# No args -> Release on CURRENT branch
command_release "current"
exit 0
fi

if [[ "$1" == "main" ]]; then
# Main arg -> Merge to MAIN and release
command_release "main"
exit 0
fi

while [[ $# -gt 0 ]]; do
case "$1" in
-h|--help) show_help; exit 0 ;;
-ver) show_version; exit 0 ;;
-l|--list) command_list_status; exit 0 ;;
-d)
shift
files_to_delete=()
while [[ $# -gt 0 && ! "$1" =~ ^- ]]; do files_to_delete+=("$1"); shift; done
command_delete_files "${files_to_delete[@]}"
;;
-no)
shift; while [[ $# -gt 0 && ! "$1" =~ ^- ]]; do command_deny_file "$1"; shift; done
;;
-yes)
shift; while [[ $# -gt 0 && ! "$1" =~ ^- ]]; do command_allow_file "$1"; shift; done
;;
*) echo -e "${RED}Unknown option: $1${NC}"; show_help; exit 1 ;;
esac

Loading

v0.3.5

v0.3.5

Choose a tag to compare

View all tags
@babakskr babakskr released this 31 Jan 22:58
v0.3.5
d6bfec6

🚀 Release v0.3.5

Automated release via git_op.sh

📄 docs/AI_DEV_GUIDELINES.md

  • Type: Description of change...

📄 git_op.sh

     if [[ -n "$notes" ]]; then 
        release_body="${release_body}"$'\n### 📄 '"$file"$'\n'"$notes"$'\n'
     fi
done < <(git grep -l "<component_release_notes>")

git commit -m "release: $target_tag (Docs Updated)"
check_error

echo ">> Pushing to $target_branch..."
git push origin "$target_branch"
check_error

echo ">> Pushing tag..."
git tag -a "$target_tag" -m "Release $target_tag"
git push origin "$target_tag"
check_error

if command -v gh &> /dev/null; then
    gh release create "$target_tag" --title "$target_tag" --notes "$release_body"
    echo -e "${GREEN}✅ Released on GitHub!${NC}"
else
    echo -e "${YELLOW}GitHub CLI missing. Local release only.${NC}"
fi

# If we switched to main, stay there? Or go back? Usually staying on main is safer after release.
# If users want to go back, they can checkout dev again.

}

--- MAIN EXECUTION ---

if [[ $# -eq 0 ]]; then
# No args -> Release on CURRENT branch
command_release "current"
exit 0
fi

if [[ "$1" == "main" ]]; then
# Main arg -> Merge to MAIN and release
command_release "main"
exit 0
fi

while [[ $# -gt 0 ]]; do
case "$1" in
-h|--help) show_help; exit 0 ;;
-ver) show_version; exit 0 ;;
-l|--list) command_list_status; exit 0 ;;
-d)
shift
files_to_delete=()
while [[ $# -gt 0 && ! "$1" =~ ^- ]]; do files_to_delete+=("$1"); shift; done
command_delete_files "${files_to_delete[@]}"
;;
-no)
shift; while [[ $# -gt 0 && ! "$1" =~ ^- ]]; do command_deny_file "$1"; shift; done
;;
-yes)
shift; while [[ $# -gt 0 && ! "$1" =~ ^- ]]; do command_allow_file "$1"; shift; done
;;
*) echo -e "${RED}Unknown option: $1${NC}"; show_help; exit 1 ;;
esac

Loading

v0.3.4

v0.3.4

Choose a tag to compare

View all tags
@babakskr babakskr released this 31 Jan 22:43
v0.3.4
6067d6b

🚀 Release v0.3.4

Automated release via git_op.sh

📄 docs/AI_DEV_GUIDELINES.md

  • Type: Description of change...

📄 git_op.sh

     if [[ -n "$notes" ]]; then 
        release_body="${release_body}"$'\n### 📄 '"$file"$'\n'"$notes"$'\n'
     fi
done < <(git grep -l "<component_release_notes>")

git commit -m "release: $target_tag (Docs Updated)"
check_error

echo ">> Pushing to $target_branch..."
git push origin "$target_branch"
check_error

echo ">> Pushing tag..."
git tag -a "$target_tag" -m "Release $target_tag"
git push origin "$target_tag"
check_error

if command -v gh &> /dev/null; then
    gh release create "$target_tag" --title "$target_tag" --notes "$release_body"
    echo -e "${GREEN}✅ Released on GitHub!${NC}"
else
    echo -e "${YELLOW}GitHub CLI missing. Local release only.${NC}"
fi

# If we switched to main, stay there? Or go back? Usually staying on main is safer after release.
# If users want to go back, they can checkout dev again.

}

--- MAIN EXECUTION ---

if [[ $# -eq 0 ]]; then
# No args -> Release on CURRENT branch
command_release "current"
exit 0
fi

if [[ "$1" == "main" ]]; then
# Main arg -> Merge to MAIN and release
command_release "main"
exit 0
fi

while [[ $# -gt 0 ]]; do
case "$1" in
-h|--help) show_help; exit 0 ;;
-ver) show_version; exit 0 ;;
-l|--list) command_list_status; exit 0 ;;
-d)
shift
files_to_delete=()
while [[ $# -gt 0 && ! "$1" =~ ^- ]]; do files_to_delete+=("$1"); shift; done
command_delete_files "${files_to_delete[@]}"
;;
-no)
shift; while [[ $# -gt 0 && ! "$1" =~ ^- ]]; do command_deny_file "$1"; shift; done
;;
-yes)
shift; while [[ $# -gt 0 && ! "$1" =~ ^- ]]; do command_allow_file "$1"; shift; done
;;
*) echo -e "${RED}Unknown option: $1${NC}"; show_help; exit 1 ;;
esac

Loading

v0.2.26

v0.2.26

Choose a tag to compare

View all tags
@babakskr babakskr released this 30 Jan 19:00
v0.2.26
95f6b19

🚀 Release v0.2.26

Automated release via git_op.sh

📄 conduit-optimizer.sh

  • Documentation: Updated -h to include detailed descriptions and usage examples.
  • Standard: Aligned with new CLI standards (Detailed Help).

📄 docs/AI_DEV_GUIDELINES.md

  • Type: Description of change...

📄 git_op.sh

     if [[ -n "$notes" ]]; then 
        release_body="${release_body}"$'\n### 📄 '"$file"$'\n'"$notes"$'\n'
     fi
done < <(git grep -l "<component_release_notes>")

git commit -m "release: $target_tag (Docs Updated)"
check_error

echo ">> Pushing to $target_branch..."
git push origin "$target_branch"
check_error

echo ">> Pushing tag..."
git tag -a "$target_tag" -m "Release $target_tag"
git push origin "$target_tag"
check_error

if command -v gh &> /dev/null; then
    gh release create "$target_tag" --title "$target_tag" --notes "$release_body"
    echo -e "${GREEN}✅ Released on GitHub!${NC}"
else
    echo -e "${YELLOW}GitHub CLI missing. Local release only.${NC}"
fi

# If we switched to main, stay there? Or go back? Usually staying on main is safer after release.
# If users want to go back, they can checkout dev again.

}

--- MAIN EXECUTION ---

if [[ $# -eq 0 ]]; then
# No args -> Release on CURRENT branch
command_release "current"
exit 0
fi

if [[ "$1" == "main" ]]; then
# Main arg -> Merge to MAIN and release
command_release "main"
exit 0
fi

while [[ $# -gt 0 ]]; do
case "$1" in
-h|--help) show_help; exit 0 ;;
-ver) show_version; exit 0 ;;
-l|--list) command_list_status; exit 0 ;;
-d)
shift
files_to_delete=()
while [[ $# -gt 0 && ! "$1" =~ ^- ]]; do files_to_delete+=("$1"); shift; done
command_delete_files "${files_to_delete[@]}"
;;
-no)
shift; while [[ $# -gt 0 && ! "$1" =~ ^- ]]; do command_deny_file "$1"; shift; done
;;
-yes)
shift; while [[ $# -gt 0 && ! "$1" =~ ^- ]]; do command_allow_file "$1"; shift; done
;;
*) echo -e "${RED}Unknown option: $1${NC}"; show_help; exit 1 ;;
esac

Loading

v0.2.25

v0.2.25

Choose a tag to compare

View all tags
@babakskr babakskr released this 30 Jan 18:59
v0.2.25
80e5a26

🚀 Release v0.2.25

Automated release via git_op.sh

📄 conduit-optimizer.sh

  • Documentation: Updated -h to include detailed descriptions and usage examples.
  • Standard: Aligned with new CLI standards (Detailed Help).

📄 docs/AI_DEV_GUIDELINES.md

  • Type: Description of change...

📄 git_op.sh

     if [[ -n "$notes" ]]; then 
        release_body="${release_body}"$'\n### 📄 '"$file"$'\n'"$notes"$'\n'
     fi
done < <(git grep -l "<component_release_notes>")

git commit -m "release: $target_tag (Docs Updated)"
check_error

echo ">> Pushing to $target_branch..."
git push origin "$target_branch"
check_error

echo ">> Pushing tag..."
git tag -a "$target_tag" -m "Release $target_tag"
git push origin "$target_tag"
check_error

if command -v gh &> /dev/null; then
    gh release create "$target_tag" --title "$target_tag" --notes "$release_body"
    echo -e "${GREEN}✅ Released on GitHub!${NC}"
else
    echo -e "${YELLOW}GitHub CLI missing. Local release only.${NC}"
fi

# If we switched to main, stay there? Or go back? Usually staying on main is safer after release.
# If users want to go back, they can checkout dev again.

}

--- MAIN EXECUTION ---

if [[ $# -eq 0 ]]; then
# No args -> Release on CURRENT branch
command_release "current"
exit 0
fi

if [[ "$1" == "main" ]]; then
# Main arg -> Merge to MAIN and release
command_release "main"
exit 0
fi

while [[ $# -gt 0 ]]; do
case "$1" in
-h|--help) show_help; exit 0 ;;
-ver) show_version; exit 0 ;;
-l|--list) command_list_status; exit 0 ;;
-d)
shift
files_to_delete=()
while [[ $# -gt 0 && ! "$1" =~ ^- ]]; do files_to_delete+=("$1"); shift; done
command_delete_files "${files_to_delete[@]}"
;;
-no)
shift; while [[ $# -gt 0 && ! "$1" =~ ^- ]]; do command_deny_file "$1"; shift; done
;;
-yes)
shift; while [[ $# -gt 0 && ! "$1" =~ ^- ]]; do command_allow_file "$1"; shift; done
;;
*) echo -e "${RED}Unknown option: $1${NC}"; show_help; exit 1 ;;
esac

Loading

v0.2.24

v0.2.24

Choose a tag to compare

View all tags
@babakskr babakskr released this 30 Jan 18:58
v0.2.24
3a7d52e

🚀 Release v0.2.24

Automated release via git_op.sh

📄 conduit-optimizer.sh

  • Documentation: Updated -h to include detailed descriptions and usage examples.
  • Standard: Aligned with new CLI standards (Detailed Help).

📄 docs/AI_DEV_GUIDELINES.md

  • Type: Description of change...

📄 git_op.sh

     if [[ -n "$notes" ]]; then 
        release_body="${release_body}"$'\n### 📄 '"$file"$'\n'"$notes"$'\n'
     fi
done < <(git grep -l "<component_release_notes>")

git commit -m "release: $target_tag (Docs Updated)"
check_error

echo ">> Pushing to $target_branch..."
git push origin "$target_branch"
check_error

echo ">> Pushing tag..."
git tag -a "$target_tag" -m "Release $target_tag"
git push origin "$target_tag"
check_error

if command -v gh &> /dev/null; then
    gh release create "$target_tag" --title "$target_tag" --notes "$release_body"
    echo -e "${GREEN}✅ Released on GitHub!${NC}"
else
    echo -e "${YELLOW}GitHub CLI missing. Local release only.${NC}"
fi

# If we switched to main, stay there? Or go back? Usually staying on main is safer after release.
# If users want to go back, they can checkout dev again.

}

--- MAIN EXECUTION ---

if [[ $# -eq 0 ]]; then
# No args -> Release on CURRENT branch
command_release "current"
exit 0
fi

if [[ "$1" == "main" ]]; then
# Main arg -> Merge to MAIN and release
command_release "main"
exit 0
fi

while [[ $# -gt 0 ]]; do
case "$1" in
-h|--help) show_help; exit 0 ;;
-ver) show_version; exit 0 ;;
-l|--list) command_list_status; exit 0 ;;
-d)
shift
files_to_delete=()
while [[ $# -gt 0 && ! "$1" =~ ^- ]]; do files_to_delete+=("$1"); shift; done
command_delete_files "${files_to_delete[@]}"
;;
-no)
shift; while [[ $# -gt 0 && ! "$1" =~ ^- ]]; do command_deny_file "$1"; shift; done
;;
-yes)
shift; while [[ $# -gt 0 && ! "$1" =~ ^- ]]; do command_allow_file "$1"; shift; done
;;
*) echo -e "${RED}Unknown option: $1${NC}"; show_help; exit 1 ;;
esac

Loading

v0.2.23

v0.2.23

Choose a tag to compare

View all tags
@babakskr babakskr released this 30 Jan 18:56
v0.2.23
d316dec

🚀 Release v0.2.23

Automated release via git_op.sh

📄 conduit-optimizer.sh

  • Documentation: Updated -h to include detailed descriptions and usage examples.
  • Standard: Aligned with new CLI standards (Detailed Help).

📄 docs/AI_DEV_GUIDELINES.md

  • Type: Description of change...

📄 git_op.sh

     if [[ -n "$notes" ]]; then 
        release_body="${release_body}"$'\n### 📄 '"$file"$'\n'"$notes"$'\n'
     fi
done < <(git grep -l "<component_release_notes>")

git commit -m "release: $target_tag (Docs Updated)"
check_error

echo ">> Pushing to $target_branch..."
git push origin "$target_branch"
check_error

echo ">> Pushing tag..."
git tag -a "$target_tag" -m "Release $target_tag"
git push origin "$target_tag"
check_error

if command -v gh &> /dev/null; then
    gh release create "$target_tag" --title "$target_tag" --notes "$release_body"
    echo -e "${GREEN}✅ Released on GitHub!${NC}"
else
    echo -e "${YELLOW}GitHub CLI missing. Local release only.${NC}"
fi

# If we switched to main, stay there? Or go back? Usually staying on main is safer after release.
# If users want to go back, they can checkout dev again.

}

--- MAIN EXECUTION ---

if [[ $# -eq 0 ]]; then
# No args -> Release on CURRENT branch
command_release "current"
exit 0
fi

if [[ "$1" == "main" ]]; then
# Main arg -> Merge to MAIN and release
command_release "main"
exit 0
fi

while [[ $# -gt 0 ]]; do
case "$1" in
-h|--help) show_help; exit 0 ;;
-ver) show_version; exit 0 ;;
-l|--list) command_list_status; exit 0 ;;
-d)
shift
files_to_delete=()
while [[ $# -gt 0 && ! "$1" =~ ^- ]]; do files_to_delete+=("$1"); shift; done
command_delete_files "${files_to_delete[@]}"
;;
-no)
shift; while [[ $# -gt 0 && ! "$1" =~ ^- ]]; do command_deny_file "$1"; shift; done
;;
-yes)
shift; while [[ $# -gt 0 && ! "$1" =~ ^- ]]; do command_allow_file "$1"; shift; done
;;
*) echo -e "${RED}Unknown option: $1${NC}"; show_help; exit 1 ;;
esac

Loading

v0.2.22

v0.2.22

Choose a tag to compare

View all tags
@babakskr babakskr released this 30 Jan 18:56
v0.2.22
4af0f44

🚀 Release v0.2.22

Automated release via git_op.sh

📄 conduit-optimizer.sh

  • Documentation: Updated -h to include detailed descriptions and usage examples.
  • Standard: Aligned with new CLI standards (Detailed Help).

📄 docs/AI_DEV_GUIDELINES.md

  • Type: Description of change...

📄 git_op.sh

     if [[ -n "$notes" ]]; then 
        release_body="${release_body}"$'\n### 📄 '"$file"$'\n'"$notes"$'\n'
     fi
done < <(git grep -l "<component_release_notes>")

git commit -m "release: $target_tag (Docs Updated)"
check_error

echo ">> Pushing to $target_branch..."
git push origin "$target_branch"
check_error

echo ">> Pushing tag..."
git tag -a "$target_tag" -m "Release $target_tag"
git push origin "$target_tag"
check_error

if command -v gh &> /dev/null; then
    gh release create "$target_tag" --title "$target_tag" --notes "$release_body"
    echo -e "${GREEN}✅ Released on GitHub!${NC}"
else
    echo -e "${YELLOW}GitHub CLI missing. Local release only.${NC}"
fi

# If we switched to main, stay there? Or go back? Usually staying on main is safer after release.
# If users want to go back, they can checkout dev again.

}

--- MAIN EXECUTION ---

if [[ $# -eq 0 ]]; then
# No args -> Release on CURRENT branch
command_release "current"
exit 0
fi

if [[ "$1" == "main" ]]; then
# Main arg -> Merge to MAIN and release
command_release "main"
exit 0
fi

while [[ $# -gt 0 ]]; do
case "$1" in
-h|--help) show_help; exit 0 ;;
-ver) show_version; exit 0 ;;
-l|--list) command_list_status; exit 0 ;;
-d)
shift
files_to_delete=()
while [[ $# -gt 0 && ! "$1" =~ ^- ]]; do files_to_delete+=("$1"); shift; done
command_delete_files "${files_to_delete[@]}"
;;
-no)
shift; while [[ $# -gt 0 && ! "$1" =~ ^- ]]; do command_deny_file "$1"; shift; done
;;
-yes)
shift; while [[ $# -gt 0 && ! "$1" =~ ^- ]]; do command_allow_file "$1"; shift; done
;;
*) echo -e "${RED}Unknown option: $1${NC}"; show_help; exit 1 ;;
esac

Loading

Release v1.5.0

Release v1.5.0

Choose a tag to compare

View all tags
@babakskr babakskr released this 29 Jan 14:29
v1.5.0
639367b

?? Release v1.5.0: CLI & Custom Priorities

Key Changes:

  • New CLI Args: Added -dock and -srv to set custom target priorities manually.
  • Logic Update: Inputs now map to Linux PRI column (Target 10 = Nice -10).
  • Verbose Mode: Added -v for detailed output logging.
  • Help Menu: Added -h for quick usage guide.
  • Safety Range: Inputs restricted to 5-20 (0 to skip).
Loading