2.1.21_dependencies_locked

[Tharickv75]

Type of Change

What type of change does this PR introduce? Mark all that apply:

• 🐛 Bug Fix
• 🚀 Feature Request
• 🔄 Refactor
• 📖 Documentation Update
• 🔧 Other (Please specify): Dependency version locking

---

Summary

What does this PR address?

• Locks all project dependencies to specific versions compatible with jivas 2.1.20
• Ensures consistent and reproducible builds by preventing unexpected dependency updates

---

Description

Bug Fixes:

• Issue: Potential compatibility issues and build inconsistencies due to floating dependency versions
• Root Cause: Dependencies were not pinned to specific versions, allowing automatic updates that could introduce breaking changes
• Resolution: All dependencies are now locked to specific versions known to work with jivas 2.1.20

Other:

• Description: Dependency version locking for build stability
• Motivation: To prevent build failures and runtime issues caused by incompatible dependency updates
• Implementation: Updated package.json/requirements.txt to use exact version numbers for all dependencies

---

Changes Made

High-Level Summary:

1. Locked all core dependencies to versions compatible with jivas 2.1.20
2. Updated dependency configuration files to use exact version numbers
3. Added documentation about dependency versioning policy

---

Checklist

Mark all that apply:

• Code follows the project's coding guidelines.
• Tests have been added or updated for new functionality.
• Documentation has been updated (if applicable).
• Existing tests pass locally with these changes.
• Any dependencies introduced are justified and documented.

---

Steps to Test

Provide a clear set of steps for testing the changes introduced in this PR:

1. Clean install dependencies using package manager (npm install, pip install, etc.)
2. Verify all dependencies resolve to exact versions specified
3. Run build process to ensure no compatibility issues
4. Execute test suite to confirm functionality remains unchanged
5. Verify application starts and operates normally

---

Additional Context

This change improves build stability and reproducibility by preventing the "dependency drift" that can occur when using version ranges. All dependencies are now explicitly pinned to versions known to work well together.

---

Questions or Concerns

• Should we consider implementing a dependency update bot for security patches?
• Are there any specific dependencies that should remain flexible for any reason?

[github-actions]

☂️ Python Coverage

current status: ✅

Overall Coverage

Lines	Covered	Coverage	Threshold	Status
649	583	90%	80%	🟢

New Files

No new covered files...

Modified Files

File	Coverage	Status
_init_.py	100%	🟢
TOTAL	100%	🟢

updated for commit: 85337fa by action🐍